Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 9.393692016601562e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 32.18948745727539s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.5939245223999023s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.0004210472106933594s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.2159347534179688e-05s
INFO | --- Analysis for 0080-3626 took 124.95471858978271s
Availability | SPARQL endpoint availability check for 土地利用图 took 0.00010395050048828125s
Availability | VoID file availability check for 土地利用图 took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for 土地利用图 took 31.788724184036255s
Reputation | Calculation of the PageRank for 土地利用图 took 0.020864009857177734s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 5.364418029785156e-05s
Believability | Calculation of trust value for 土地利用图 took 1.1920928955078125e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 163.24091792106628s
Availability | SPARQL endpoint availability check for 113322 took 9.083747863769531e-05s
Availability | VoID file availability check for 113322 took 0.0007467269897460938s
Completeness | Calculation of interlinking completeness for 113322 took 0.374042272567749s
Reputation | Calculation of the PageRank for 113322 took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for 113322 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for 113322 took 3.337860107421875e-05s
Believability | Calculation of trust value for 113322 took 1.2159347534179688e-05s
INFO | --- Analysis for 11 took 61.000911235809326s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.220008850097656e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.3241536617279053s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.020609617233276367s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.24249267578125e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.1444091796875e-05s
INFO | --- Analysis for 12323 took 57.800132036209106s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.07797908782958984s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 26.12150812149048s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 9.34600830078125e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.430511474609375e-05s
INFO | --- Analysis for 2000-us-census-rdf took 150.01302814483643s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.7103781700134277s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 25.388161420822144s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.02247762680053711s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.000823974609375s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 5.078315734863281e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 9.059906005859375e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 114.38524436950684s
Availability | SPARQL endpoint availability check for Open Data Web took 18.12414026260376s
Availability | VoID file availability check for Open Data Web took 0.00035309791564941406s
Completeness | Calculation of interlinking completeness for Open Data Web took 28.945478200912476s
Reputation | Calculation of the PageRank for Open Data Web took 0.020991086959838867s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 4.9591064453125e-05s
Believability | Calculation of trust value for Open Data Web took 1.1682510375976562e-05s
INFO | --- Analysis for _data.odw.tw took 117.72942781448364s
Availability | SPARQL endpoint availability check for 土地利用 took 0.00017404556274414062s
Availability | VoID file availability check for 土地利用 took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.33501720428466797s
Reputation | Calculation of the PageRank for 土地利用 took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.24249267578125e-05s
Believability | Calculation of trust value for 土地利用 took 1.1920928955078125e-05s
INFO | --- Analysis for _data1.odw.tw took 81.1353828907013s
Availability | SPARQL endpoint availability check for 土地利用模型 took 9.799003601074219e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.3379511833190918s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020652294158935547s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 3.314018249511719e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.2159347534179688e-05s
INFO | --- Analysis for _data2.odw.tw took 143.6275873184204s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 6.389617919921875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 27.516908884048462s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020964384078979492s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.8623809814453125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.5735626220703125e-05s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 135.2358582019806s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 9.250640869140625e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.3067939281463623s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020887374877929688s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 4.0531158447265625e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.2159347534179688e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 109.13440704345703s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 0.000110626220703125s
Availability | VoID file availability check for ITS TEST DATASET took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.40987396240234375s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.021660327911376953s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.910064697265625e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 9.5367431640625e-06s
INFO | --- Analysis for A1 took 161.75260543823242s
Availability | SPARQL endpoint availability check for SummerOlympics took 4.7910075187683105s
Availability | VoID file availability check for SummerOlympics took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.31147193908691406s
Reputation | Calculation of the PageRank for SummerOlympics took 0.020898103713989258s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 7.033348083496094e-05s
Believability | Calculation of trust value for SummerOlympics took 1.239776611328125e-05s
INFO | --- Analysis for abc took 168.19950556755066s
Availability | SPARQL endpoint availability check for Test_m took 0.00017523765563964844s
Availability | VoID file availability check for Test_m took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Test_m took 31.83452272415161s
Reputation | Calculation of the PageRank for Test_m took 0.020634174346923828s
Interlinking | Calculation of Degree of Connection for Test_m took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.24249267578125e-05s
Believability | Calculation of trust value for Test_m took 7.867813110351562e-06s
INFO | --- Analysis for ABC took 61.097633361816406s
Availability | SPARQL endpoint availability check for my intro took 4.649162292480469e-05s
Availability | VoID file availability check for my intro took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for my intro took 0.31520676612854004s
Reputation | Calculation of the PageRank for my intro took 0.022302865982055664s
Interlinking | Calculation of Degree of Connection for my intro took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for my intro took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for my intro took 4.363059997558594e-05s
Believability | Calculation of trust value for my intro took 1.3113021850585938e-05s
INFO | --- Analysis for abhay_intro took 112.86268854141235s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.10240054130554199s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.3905024528503418s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.02063465118408203s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.000102996826171875s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for abs-linked-data took 59.97235989570618s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 261.4519817829132s
Availability | VoID file availability check for Academic Offer of UNL took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.3331882953643799s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 3.528594970703125e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 1.2636184692382812e-05s
INFO | --- Analysis for academic-offer-of-unl took 677.7212693691254s
Availability | SPARQL endpoint availability check for AcadOnto took 8.797645568847656e-05s
Availability | VoID file availability check for AcadOnto took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for AcadOnto took 32.50687313079834s
Reputation | Calculation of the PageRank for AcadOnto took 0.021458148956298828s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 4.029273986816406e-05s
Believability | Calculation of trust value for AcadOnto took 1.1205673217773438e-05s
INFO | --- Analysis for acadonto took 179.80824828147888s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 10.456368446350098s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 26.709123373031616s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.022195100784301758s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.910064697265625e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 8.821487426757812e-06s
INFO | --- Analysis for acorn-sat took 174.74824786186218s
Availability | SPARQL endpoint availability check for Addgene took 4.410743713378906e-05s
Availability | VoID file availability check for Addgene took 0.0009486675262451172s
Completeness | Calculation of interlinking completeness for Addgene took 24.737648248672485s
Reputation | Calculation of the PageRank for Addgene took 0.020888805389404297s
Interlinking | Calculation of Degree of Connection for Addgene took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Addgene took 4.863739013671875e-05s
Believability | Calculation of trust value for Addgene took 1.1444091796875e-05s
INFO | --- Analysis for addgene took 208.88747930526733s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 5.5789947509765625e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0007500648498535156s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.32054615020751953s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.393692016601562e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.0967254638671875e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 57.918930530548096s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.48952579498291016s
Availability | VoID file availability check for AEMET metereological dataset took 0.26767754554748535s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 29.062907457351685s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020853519439697266s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for AEMET metereological dataset took 2.1457672119140625e-06s
Believability | Calculation of trust value for AEMET metereological dataset took 8.58306884765625e-06s
INFO | --- Analysis for aemet took 163.7090802192688s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 9.989738464355469e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.30377793312072754s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02091073989868164s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0008707046508789062s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 3.719329833984375e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 1.2874603271484375e-05s
INFO | --- Analysis for agenda-de-zaragoza took 87.29177737236023s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.04545712471008301s
Availability | VoID file availability check for AgriNepalData took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for AgriNepalData took 31.8435537815094s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020843029022216797s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.43865966796875e-05s
Believability | Calculation of trust value for AgriNepalData took 8.344650268554688e-06s
INFO | --- Analysis for agrinepaldata took 134.99558925628662s
Availability | SPARQL endpoint availability check for AGRIS took 262.4615800380707s
Availability | VoID file availability check for AGRIS took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for AGRIS took 0.32102370262145996s
Reputation | Calculation of the PageRank for AGRIS took 0.021348237991333008s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for AGRIS took 9.298324584960938e-05s
Believability | Calculation of trust value for AGRIS took 7.867813110351562e-06s
INFO | --- Analysis for agris took 646.0897569656372s
Availability | SPARQL endpoint availability check for AGROVOC took 0.20757389068603516s
Availability | VoID file availability check for AGROVOC took 0.0007238388061523438s
Extra | Recovery of all triples for AGROVOC took 86.3276937007904s
Performance | Total latancy measurement for AGROVOC took 0.4963698387145996s
Amount of data | Number of triples check for AGROVOC took 64.10431981086731s
Interoperability | New terms check for AGROVOC took 3.6485483646392822s
Versatility | Languages check for AGROVOC took 105.10975503921509s
Interpretability | Number of blank nodes check for AGROVOC took 68.7553141117096s
Interpretability | RDF structures check for AGROVOC took 0.15945005416870117s
Versatility | Serialization formats check for AGROVOC took 0.0972909927368164s
Availability | RDF dump link check for AGROVOC took 0.07564640045166016s
License | MR license check for AGROVOC took 0.07737398147583008s
License | HR license check for AGROVOC took 0.39121413230895996s
Amount of data | Number of property check for AGROVOC took 0.07763242721557617s
Understandability | Number of label check for AGROVOC took 55.682600259780884s
Understandability | URI regex check for AGROVOC took 0.16543984413146973s
Understandability | Vocabs check for AGROVOC took 0.087249755859375s
Verifiability | Authors check for AGROVOC took 0.09803581237792969s
Verifiability | Publishers check for AGROVOC took 0.09968304634094238s
Performance | Throughput check for AGROVOC took 10.339439630508423s
Amount of data | Check the number of entities for AGROVOC took 7.152557373046875e-05s
Verifiability | Contribs. check for AGROVOC took 0.10047245025634766s
Interlinking | sameAs chians check for AGROVOC took 0.10018181800842285s
Interlinking | skos check for AGROVOC took 2.2907865047454834s
Interlinking | skos check for AGROVOC took 1.924586534500122s
Timeliness | dataset update frequency check for AGROVOC took 0.07690000534057617s
Currency | Creation date check for AGROVOC took 0.18116092681884766s
Currency | Modification date check for AGROVOC took 0.16469240188598633s
Rep.Conc. | URIs length for AGROVOC took 142.19824767112732s
Interoperability | New vocabularies check for AGROVOC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.08595967292785645s
Accuracy | Check Functional Property for AGROVOC took 0.0738673210144043s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.09480643272399902s
Accuracy | Check Empty annotation labels for AGROVOC took 20.26779818534851s
Accuracy | Check White space in annotation for AGROVOC took 3.041260242462158s
Accuracy | Check Datatype consistency for AGROVOC took 4.617361307144165s
Consistency | Disjoint class check for AGROVOC took 0.09728074073791504s
Consistency | Check Misplaced properties for AGROVOC took 15.591098546981812s
Consistency | Check Ontology hijacking for AGROVOC took 119.27080130577087s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.679900884628296s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 21.808430671691895s
Conciseness | Check Extensional conciseness for AGROVOC took 2.608670473098755s
Conciseness | Check Intensional conciseness for AGROVOC took 0.09876275062561035s
Security | Sign check for AGROVOC took 0.08943986892700195s
Availability | Check URIs Dereferenciability for AGROVOC took 3.129565715789795s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.4811363220214844s
Reputation | Calculation of the PageRank for AGROVOC took 0.02165818214416504s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011849403381347656s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 2.384185791015625e-06s
Believability | Calculation of trust value for AGROVOC took 1.1682510375976562e-05s
INFO | --- Analysis for agrovoc took 1144.773106098175s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.8909695148468018s
Availability | VoID file availability check for Analytics India Magazine took 0.0006377696990966797s
Extra | Recovery of all triples for Analytics India Magazine took 2.7278788089752197s
Performance | Total latancy measurement for Analytics India Magazine took 2.2815704345703125s
Amount of data | Number of triples check for Analytics India Magazine took 1.1617672443389893s
Versatility | Languages check for Analytics India Magazine took 1.0488100051879883s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.1660492420196533s
Interpretability | RDF structures check for Analytics India Magazine took 1.085573434829712s
Versatility | Serialization formats check for Analytics India Magazine took 1.0682389736175537s
Availability | RDF dump link check for Analytics India Magazine took 1.2762959003448486s
License | MR license check for Analytics India Magazine took 1.2395672798156738s
License | HR license check for Analytics India Magazine took 1.71299409866333s
Amount of data | Number of property check for Analytics India Magazine took 1.203449010848999s
Understandability | Number of label check for Analytics India Magazine took 1.3948633670806885s
Understandability | URI regex check for Analytics India Magazine took 2.8947625160217285s
Understandability | Vocabs check for Analytics India Magazine took 1.2748169898986816s
Verifiability | Authors check for Analytics India Magazine took 1.0224535465240479s
Verifiability | Publishers check for Analytics India Magazine took 1.4319946765899658s
Performance | Throughput check for Analytics India Magazine took 16.85585117340088s
Amount of data | Check the number of entities for Analytics India Magazine took 0.00013136863708496094s
Verifiability | Contribs. check for Analytics India Magazine took 1.174942970275879s
Interlinking | sameAs chians check for Analytics India Magazine took 1.1729414463043213s
Interlinking | skos check for Analytics India Magazine took 1.0579783916473389s
Interlinking | skos check for Analytics India Magazine took 0.1107480525970459s
Timeliness | dataset update frequency check for Analytics India Magazine took 1.3058545589447021s
Currency | Creation date check for Analytics India Magazine took 2.3674540519714355s
Currency | Modification date check for Analytics India Magazine took 2.462010383605957s
Rep.Conc. | URIs length for Analytics India Magazine took 2.8037564754486084s
Interoperability | New vocabularies check for Analytics India Magazine took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 1.0562500953674316s
Consistency | Disjoint class check for Analytics India Magazine took 1.1650328636169434s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.916170358657837s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 2.7354750633239746s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.00015544891357421875s
Security | Sign check for Analytics India Magazine took 1.6045165061950684s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.33143138885498047s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.2832775115966797s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.504753112792969e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 7.152557373046875e-07s
Believability | Calculation of trust value for Analytics India Magazine took 7.867813110351562e-06s
INFO | --- Analysis for AIM took 206.59009790420532s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 9.489059448242188e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 28.524409532546997s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.022958040237426758s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.361701965332031e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.1205673217773438e-05s
INFO | --- Analysis for AISHE took 89.74305558204651s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.649162292480469e-05s
Availability | VoID file availability check for  equipment ontology took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for  equipment ontology took 26.620460033416748s
Reputation | Calculation of the PageRank for  equipment ontology took 0.02252793312072754s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.000934600830078125s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.6716461181640625e-05s
Believability | Calculation of trust value for  equipment ontology took 1.2159347534179688e-05s
INFO | --- Analysis for akash took 29.34495449066162s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 263.6978073120117s
Availability | VoID file availability check for aliada-scanbit-net took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 31.28932785987854s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.021720170974731445s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0012116432189941406s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00015282630920410156s
Believability | Calculation of trust value for aliada-scanbit-net took 1.1920928955078125e-05s
INFO | --- Analysis for aliada-scanbit-net took 1755.983022928238s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.9019458293914795s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0007519721984863281s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 138.02462482452393s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.718374729156494s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.8320090770721436s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.631788492202759s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.0224840641022s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.8647613525390625s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8907036781311035s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.9447474479675293s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.7423152923583984s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5583634376525879s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.6712427139282227s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 31.77535057067871s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.573997974395752s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.7525184154510498s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1448493003845215s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.6107096672058105s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6473941802978516s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.6585252285003662s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 11.123536825180054s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 0.00010633468627929688s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5630331039428711s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5666508674621582s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6585671901702881s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6415135860443115s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.6172215938568115s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.2181141376495361s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1255059242248535s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 53.69163680076599s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 1.3827059268951416s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5579280853271484s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.7453567981719971s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6333582401275635s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 34.99274921417236s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.0976243019104004s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.678405284881592s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.6299753189086914s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.546616792678833s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.898265600204468s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 32.38283705711365s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.492088794708252s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.51768445968628s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.7601966857910156s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.851780891418457s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.6242537498474121s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 13960.961908102036s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.6965458393096924s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.026171207427978516s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.001730203628540039s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 0.00016069412231445312s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 1.3916471004486084s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.0967254638671875e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 14801.887972354889s
Availability | SPARQL endpoint availability check for Alojamientos took 4.291534423828125e-05s
Availability | VoID file availability check for Alojamientos took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Alojamientos took 27.698542833328247s
Reputation | Calculation of the PageRank for Alojamientos took 0.021252870559692383s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 4.220008850097656e-05s
Believability | Calculation of trust value for Alojamientos took 1.33514404296875e-05s
INFO | --- Analysis for alojamientos-zaragoza took 228.76353406906128s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.2777585983276367s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 29.443570375442505s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.021805286407470703s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0009214878082275391s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 5.745887756347656e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.1682510375976562e-05s
INFO | --- Analysis for alpino-rdf took 200.7066788673401s
Availability | SPARQL endpoint availability check for AAT-atawil took 9.298324584960938e-05s
Availability | VoID file availability check for AAT-atawil took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.31060171127319336s
Reputation | Calculation of the PageRank for AAT-atawil took 0.0208284854888916s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.170967102050781e-05s
Believability | Calculation of trust value for AAT-atawil took 1.049041748046875e-05s
INFO | --- Analysis for Altawil took 61.2332558631897s
Availability | SPARQL endpoint availability check for Amer Nejma took 9.226799011230469e-05s
Availability | VoID file availability check for Amer Nejma took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.32638072967529297s
Reputation | Calculation of the PageRank for Amer Nejma took 0.021134376525878906s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.743171691894531e-05s
Believability | Calculation of trust value for Amer Nejma took 1.2636184692382812e-05s
INFO | --- Analysis for Amer_Nejma took 116.88548183441162s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.3117187023162842s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.021518230438232422s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.337860107421875e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for amon took 84.69979166984558s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7863152027130127s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.36787986755371094s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.021796226501464844s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00010943412780761719s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 7.62939453125e-06s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 114.47459363937378s
Availability | SPARQL endpoint availability check for Anime Dataset took 9.202957153320312e-05s
Availability | VoID file availability check for Anime Dataset took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.29563093185424805s
Reputation | Calculation of the PageRank for Anime Dataset took 0.02166152000427246s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0011663436889648438s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 4.315376281738281e-05s
Believability | Calculation of trust value for Anime Dataset took 7.867813110351562e-06s
INFO | --- Analysis for Anime took 55.782424449920654s
Availability | SPARQL endpoint availability check for ANNO took 5.3882598876953125e-05s
Availability | VoID file availability check for ANNO took 0.0007658004760742188s
Completeness | Calculation of interlinking completeness for ANNO took 0.30570387840270996s
Reputation | Calculation of the PageRank for ANNO took 0.02096080780029297s
Interlinking | Calculation of Degree of Connection for ANNO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.933906555175781e-05s
Believability | Calculation of trust value for ANNO took 1.2159347534179688e-05s
INFO | --- Analysis for anno took 127.71215462684631s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 9.72747802734375e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 30.842815399169922s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.021335363388061523s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 8.916854858398438e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 1.2636184692382812e-05s
INFO | --- Analysis for AntiqueCarsCollection took 169.1651885509491s
Availability | SPARQL endpoint availability check for apache took 4.601478576660156e-05s
Availability | VoID file availability check for apache took 0.0008080005645751953s
Completeness | Calculation of interlinking completeness for apache took 31.40305805206299s
Reputation | Calculation of the PageRank for apache took 0.02226710319519043s
Interlinking | Calculation of Degree of Connection for apache took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for apache took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for apache took 6.389617919921875e-05s
Believability | Calculation of trust value for apache took 1.1920928955078125e-05s
INFO | --- Analysis for apache took 148.70629930496216s
Availability | SPARQL endpoint availability check for Apertium RDF took 1.239870548248291s
Availability | VoID file availability check for Apertium RDF took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for Apertium RDF took 26.49603009223938s
Reputation | Calculation of the PageRank for Apertium RDF took 0.02083563804626465s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf took 170.6689486503601s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 6.246566772460938e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.3014402389526367s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.021024465560913086s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.792213439941406e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 87.18451714515686s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 9.226799011230469e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 29.298383235931396s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.022672176361083984s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 89.73356080055237s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 0.28274965286254883s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0007233619689941406s
Extra | Recovery of all triples for Apertium RDF EN-ES took 163.63204646110535s
Performance | Total latancy measurement for Apertium RDF EN-ES took 1.23386812210083s
Amount of data | Number of triples check for Apertium RDF EN-ES took 2.100482702255249s
Interoperability | New terms check for Apertium RDF EN-ES took 3.3219339847564697s
Versatility | Languages check for Apertium RDF EN-ES took 44.29187297821045s
Interpretability | Number of blank nodes check for Apertium RDF EN-ES took 1.214188814163208s
Security | Check HTTPS for Apertium RDF EN-ES took 0.12274312973022461s
Interpretability | RDF structures check for Apertium RDF EN-ES took 0.29601287841796875s
Versatility | Serialization formats check for Apertium RDF EN-ES took 0.27941107749938965s
Availability | RDF dump link check for Apertium RDF EN-ES took 0.27585601806640625s
License | MR license check for Apertium RDF EN-ES took 0.3001418113708496s
License | HR license check for Apertium RDF EN-ES took 0.38509321212768555s
Amount of data | Number of property check for Apertium RDF EN-ES took 0.2942218780517578s
Understandability | Number of label check for Apertium RDF EN-ES took 0.3090822696685791s
Understandability | URI regex check for Apertium RDF EN-ES took 0.5906593799591064s
Understandability | Vocabs check for Apertium RDF EN-ES took 0.29520606994628906s
Verifiability | Authors check for Apertium RDF EN-ES took 0.2787461280822754s
Verifiability | Publishers check for Apertium RDF EN-ES took 0.2950406074523926s
Performance | Throughput check for Apertium RDF EN-ES took 11.148874282836914s
Amount of data | Check the number of entities for Apertium RDF EN-ES took 7.677078247070312e-05s
Verifiability | Contribs. check for Apertium RDF EN-ES took 0.27860403060913086s
Interlinking | sameAs chians check for Apertium RDF EN-ES took 0.26799821853637695s
Interlinking | skos check for Apertium RDF EN-ES took 0.28273773193359375s
Interlinking | skos check for Apertium RDF EN-ES took 0.20719313621520996s
Timeliness | dataset update frequency check for Apertium RDF EN-ES took 0.2947261333465576s
Currency | Creation date check for Apertium RDF EN-ES took 0.5918083190917969s
Currency | Modification date check for Apertium RDF EN-ES took 0.5463411808013916s
Rep.Conc. | URIs length for Apertium RDF EN-ES took 58.57336926460266s
Interoperability | New vocabularies check for Apertium RDF EN-ES took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-ES took 0.28995442390441895s
Accuracy | Check Functional Property for Apertium RDF EN-ES took 0.2953948974609375s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-ES took 0.2755873203277588s
Accuracy | Check Empty annotation labels for Apertium RDF EN-ES took 0.7924392223358154s
Accuracy | Check White space in annotation for Apertium RDF EN-ES took 0.010373353958129883s
Accuracy | Check Datatype consistency for Apertium RDF EN-ES took 2.6497151851654053s
Consistency | Disjoint class check for Apertium RDF EN-ES took 0.2876756191253662s
Consistency | Check Misplaced properties for Apertium RDF EN-ES took 4.719946622848511s
Consistency | Misplaced classes for Apertium RDF EN-ES took 8.50478720664978s
Consistency | Check Ontology hijacking for Apertium RDF EN-ES took 44.24202251434326s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-ES took 1.616086483001709s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-ES took 5.821237325668335s
Conciseness | Check Extensional conciseness for Apertium RDF EN-ES took 2.9330615997314453s
Conciseness | Check Intensional conciseness for Apertium RDF EN-ES took 0.3231692314147949s
Security | Sign check for Apertium RDF EN-ES took 0.30111026763916016s
Availability | Check URIs Dereferenciability for Apertium RDF EN-ES took 10.185356140136719s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.46547579765319824s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.021355867385864258s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.8160552978515625e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-ES took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-en-es took 590.2960228919983s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 0.22986054420471191s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006508827209472656s
Extra | Recovery of all triples for Apertium RDF EN-GL took 161.03695559501648s
Performance | Total latancy measurement for Apertium RDF EN-GL took 1.2357940673828125s
Amount of data | Number of triples check for Apertium RDF EN-GL took 2.0988330841064453s
Interoperability | New terms check for Apertium RDF EN-GL took 3.090982437133789s
Versatility | Languages check for Apertium RDF EN-GL took 44.54059338569641s
Interpretability | Number of blank nodes check for Apertium RDF EN-GL took 1.2403976917266846s
Security | Check HTTPS for Apertium RDF EN-GL took 0.13329219818115234s
Interpretability | RDF structures check for Apertium RDF EN-GL took 0.30857086181640625s
Versatility | Serialization formats check for Apertium RDF EN-GL took 0.2888813018798828s
Availability | RDF dump link check for Apertium RDF EN-GL took 0.3061671257019043s
License | MR license check for Apertium RDF EN-GL took 0.8101439476013184s
License | HR license check for Apertium RDF EN-GL took 0.36569929122924805s
Amount of data | Number of property check for Apertium RDF EN-GL took 0.2802114486694336s
Understandability | Number of label check for Apertium RDF EN-GL took 0.31766724586486816s
Understandability | URI regex check for Apertium RDF EN-GL took 0.5858080387115479s
Understandability | Vocabs check for Apertium RDF EN-GL took 0.2847177982330322s
Verifiability | Authors check for Apertium RDF EN-GL took 0.2924339771270752s
Verifiability | Publishers check for Apertium RDF EN-GL took 0.2736694812774658s
Performance | Throughput check for Apertium RDF EN-GL took 11.120053768157959s
Amount of data | Check the number of entities for Apertium RDF EN-GL took 3.361701965332031e-05s
Verifiability | Contribs. check for Apertium RDF EN-GL took 0.3116617202758789s
Interlinking | sameAs chians check for Apertium RDF EN-GL took 0.30126500129699707s
Interlinking | skos check for Apertium RDF EN-GL took 0.2948000431060791s
Interlinking | skos check for Apertium RDF EN-GL took 0.21398448944091797s
Timeliness | dataset update frequency check for Apertium RDF EN-GL took 0.28435707092285156s
Currency | Creation date check for Apertium RDF EN-GL took 0.5681040287017822s
Currency | Modification date check for Apertium RDF EN-GL took 0.5541975498199463s
Rep.Conc. | URIs length for Apertium RDF EN-GL took 58.97837543487549s
Interoperability | New vocabularies check for Apertium RDF EN-GL took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-GL took 0.2960245609283447s
Accuracy | Check Functional Property for Apertium RDF EN-GL took 0.2974812984466553s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-GL took 0.2896454334259033s
Accuracy | Check Empty annotation labels for Apertium RDF EN-GL took 0.822751522064209s
Accuracy | Check White space in annotation for Apertium RDF EN-GL took 0.01073765754699707s
Accuracy | Check Datatype consistency for Apertium RDF EN-GL took 2.7428979873657227s
Consistency | Disjoint class check for Apertium RDF EN-GL took 0.2927529811859131s
Consistency | Check Misplaced properties for Apertium RDF EN-GL took 4.626089572906494s
Consistency | Misplaced classes for Apertium RDF EN-GL took 8.605695724487305s
Consistency | Check Ontology hijacking for Apertium RDF EN-GL took 44.638779401779175s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-GL took 1.6539630889892578s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-GL took 5.74958610534668s
Conciseness | Check Extensional conciseness for Apertium RDF EN-GL took 3.013327121734619s
Conciseness | Check Intensional conciseness for Apertium RDF EN-GL took 0.28964757919311523s
Security | Sign check for Apertium RDF EN-GL took 0.29339122772216797s
Availability | Check URIs Dereferenciability for Apertium RDF EN-GL took 9.744860410690308s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 27.703068494796753s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.02131795883178711s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 5.078315734863281e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-GL took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 521.9989988803864s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.5299530029296875e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.3303651809692383s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020875215530395508s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 5.0067901611328125e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 115.39965748786926s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 0.00015425682067871094s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0006921291351318359s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.29175567626953125s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02141714096069336s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 5.221366882324219e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 151.5805642604828s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 0.27567458152770996s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0007703304290771484s
Extra | Recovery of all triples for Apertium RDF EO-ES took 160.6318678855896s
Performance | Total latancy measurement for Apertium RDF EO-ES took 1.234389066696167s
Amount of data | Number of triples check for Apertium RDF EO-ES took 2.2399117946624756s
Interoperability | New terms check for Apertium RDF EO-ES took 3.144603729248047s
Versatility | Languages check for Apertium RDF EO-ES took 44.00022053718567s
Interpretability | Number of blank nodes check for Apertium RDF EO-ES took 1.0795860290527344s
Security | Check HTTPS for Apertium RDF EO-ES took 0.14522099494934082s
Interpretability | RDF structures check for Apertium RDF EO-ES took 0.29616689682006836s
Versatility | Serialization formats check for Apertium RDF EO-ES took 0.2809309959411621s
Availability | RDF dump link check for Apertium RDF EO-ES took 0.31038522720336914s
License | MR license check for Apertium RDF EO-ES took 0.2785155773162842s
License | HR license check for Apertium RDF EO-ES took 0.371875524520874s
Amount of data | Number of property check for Apertium RDF EO-ES took 0.28824400901794434s
Understandability | Number of label check for Apertium RDF EO-ES took 0.3084261417388916s
Understandability | URI regex check for Apertium RDF EO-ES took 0.5622951984405518s
Understandability | Vocabs check for Apertium RDF EO-ES took 0.3032815456390381s
Verifiability | Authors check for Apertium RDF EO-ES took 0.27672910690307617s
Verifiability | Publishers check for Apertium RDF EO-ES took 0.27511072158813477s
Performance | Throughput check for Apertium RDF EO-ES took 11.28710150718689s
Amount of data | Check the number of entities for Apertium RDF EO-ES took 7.486343383789062e-05s
Verifiability | Contribs. check for Apertium RDF EO-ES took 0.28455686569213867s
Interlinking | sameAs chians check for Apertium RDF EO-ES took 0.2837998867034912s
Interlinking | skos check for Apertium RDF EO-ES took 0.28769588470458984s
Interlinking | skos check for Apertium RDF EO-ES took 0.24144387245178223s
Timeliness | dataset update frequency check for Apertium RDF EO-ES took 0.2854595184326172s
Currency | Creation date check for Apertium RDF EO-ES took 0.5708823204040527s
Currency | Modification date check for Apertium RDF EO-ES took 0.5791947841644287s
Rep.Conc. | URIs length for Apertium RDF EO-ES took 58.431758880615234s
Interoperability | New vocabularies check for Apertium RDF EO-ES took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-ES took 0.2920668125152588s
Accuracy | Check Functional Property for Apertium RDF EO-ES took 0.26574254035949707s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-ES took 0.28952527046203613s
Accuracy | Check Empty annotation labels for Apertium RDF EO-ES took 0.8381788730621338s
Accuracy | Check White space in annotation for Apertium RDF EO-ES took 0.010335922241210938s
Accuracy | Check Datatype consistency for Apertium RDF EO-ES took 2.6632580757141113s
Consistency | Disjoint class check for Apertium RDF EO-ES took 0.2916715145111084s
Consistency | Check Misplaced properties for Apertium RDF EO-ES took 4.729667901992798s
Consistency | Misplaced classes for Apertium RDF EO-ES took 8.54535460472107s
Consistency | Check Ontology hijacking for Apertium RDF EO-ES took 44.385942220687866s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-ES took 1.6240911483764648s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-ES took 5.720975637435913s
Conciseness | Check Extensional conciseness for Apertium RDF EO-ES took 2.917598247528076s
Conciseness | Check Intensional conciseness for Apertium RDF EO-ES took 0.30698347091674805s
Security | Sign check for Apertium RDF EO-ES took 0.2822589874267578s
Availability | Check URIs Dereferenciability for Apertium RDF EO-ES took 10.764399766921997s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.8736767768859863s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.021118640899658203s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 5.841255187988281e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-ES took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 577.7913098335266s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 0.2406761646270752s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0007429122924804688s
Extra | Recovery of all triples for Apertium RDF EO-FR took 160.53591346740723s
Performance | Total latancy measurement for Apertium RDF EO-FR took 1.2101447582244873s
Amount of data | Number of triples check for Apertium RDF EO-FR took 2.2222397327423096s
Interoperability | New terms check for Apertium RDF EO-FR took 3.0786519050598145s
Versatility | Languages check for Apertium RDF EO-FR took 44.416948318481445s
Interpretability | Number of blank nodes check for Apertium RDF EO-FR took 1.0838828086853027s
Security | Check HTTPS for Apertium RDF EO-FR took 0.12250137329101562s
Interpretability | RDF structures check for Apertium RDF EO-FR took 0.27884340286254883s
Versatility | Serialization formats check for Apertium RDF EO-FR took 0.2949199676513672s
Availability | RDF dump link check for Apertium RDF EO-FR took 0.2839202880859375s
License | MR license check for Apertium RDF EO-FR took 0.2796363830566406s
License | HR license check for Apertium RDF EO-FR took 0.6769371032714844s
Amount of data | Number of property check for Apertium RDF EO-FR took 0.2902839183807373s
Understandability | Number of label check for Apertium RDF EO-FR took 0.31716322898864746s
Understandability | URI regex check for Apertium RDF EO-FR took 0.5853621959686279s
Understandability | Vocabs check for Apertium RDF EO-FR took 0.29790759086608887s
Verifiability | Authors check for Apertium RDF EO-FR took 0.28832221031188965s
Verifiability | Publishers check for Apertium RDF EO-FR took 0.2958557605743408s
Performance | Throughput check for Apertium RDF EO-FR took 11.12669563293457s
Amount of data | Check the number of entities for Apertium RDF EO-FR took 7.724761962890625e-05s
Verifiability | Contribs. check for Apertium RDF EO-FR took 0.28084588050842285s
Interlinking | sameAs chians check for Apertium RDF EO-FR took 0.30274224281311035s
Interlinking | skos check for Apertium RDF EO-FR took 0.2875969409942627s
Interlinking | skos check for Apertium RDF EO-FR took 0.22239208221435547s
Timeliness | dataset update frequency check for Apertium RDF EO-FR took 0.29689812660217285s
Currency | Creation date check for Apertium RDF EO-FR took 0.5533266067504883s
Currency | Modification date check for Apertium RDF EO-FR took 0.5840482711791992s
Rep.Conc. | URIs length for Apertium RDF EO-FR took 58.22973299026489s
Interoperability | New vocabularies check for Apertium RDF EO-FR took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-FR took 0.29041171073913574s
Accuracy | Check Functional Property for Apertium RDF EO-FR took 0.2796456813812256s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-FR took 0.2825183868408203s
Accuracy | Check Empty annotation labels for Apertium RDF EO-FR took 0.8600342273712158s
Accuracy | Check White space in annotation for Apertium RDF EO-FR took 0.010336875915527344s
Accuracy | Check Datatype consistency for Apertium RDF EO-FR took 2.7167587280273438s
Consistency | Disjoint class check for Apertium RDF EO-FR took 0.3031134605407715s
Consistency | Check Misplaced properties for Apertium RDF EO-FR took 4.589080572128296s
Consistency | Misplaced classes for Apertium RDF EO-FR took 8.573561191558838s
Consistency | Check Ontology hijacking for Apertium RDF EO-FR took 44.61381411552429s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-FR took 1.653907299041748s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-FR took 5.933166980743408s
Conciseness | Check Extensional conciseness for Apertium RDF EO-FR took 3.0025534629821777s
Conciseness | Check Intensional conciseness for Apertium RDF EO-FR took 0.30541467666625977s
Security | Sign check for Apertium RDF EO-FR took 0.2723526954650879s
Availability | Check URIs Dereferenciability for Apertium RDF EO-FR took 10.277113199234009s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.4375953674316406s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020891666412353516s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.9114227294921875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-FR took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 528.0662364959717s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 0.2016291618347168s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0007374286651611328s
Extra | Recovery of all triples for Apertium RDF ES-AN took 162.14056754112244s
Performance | Total latancy measurement for Apertium RDF ES-AN took 1.1810944080352783s
Amount of data | Number of triples check for Apertium RDF ES-AN took 2.150327444076538s
Interoperability | New terms check for Apertium RDF ES-AN took 3.047947645187378s
Versatility | Languages check for Apertium RDF ES-AN took 44.3050422668457s
Interpretability | Number of blank nodes check for Apertium RDF ES-AN took 1.0643336772918701s
Security | Check HTTPS for Apertium RDF ES-AN took 0.14485526084899902s
Interpretability | RDF structures check for Apertium RDF ES-AN took 0.2840583324432373s
Versatility | Serialization formats check for Apertium RDF ES-AN took 0.2876777648925781s
Availability | RDF dump link check for Apertium RDF ES-AN took 0.28151607513427734s
License | MR license check for Apertium RDF ES-AN took 0.2978949546813965s
License | HR license check for Apertium RDF ES-AN took 0.38480639457702637s
Amount of data | Number of property check for Apertium RDF ES-AN took 0.3275480270385742s
Understandability | Number of label check for Apertium RDF ES-AN took 0.32722973823547363s
Understandability | URI regex check for Apertium RDF ES-AN took 0.5866496562957764s
Understandability | Vocabs check for Apertium RDF ES-AN took 0.28603124618530273s
Verifiability | Authors check for Apertium RDF ES-AN took 0.29415440559387207s
Verifiability | Publishers check for Apertium RDF ES-AN took 0.273296594619751s
Performance | Throughput check for Apertium RDF ES-AN took 11.21422529220581s
Amount of data | Check the number of entities for Apertium RDF ES-AN took 7.152557373046875e-05s
Verifiability | Contribs. check for Apertium RDF ES-AN took 0.2882113456726074s
Interlinking | sameAs chians check for Apertium RDF ES-AN took 0.2716524600982666s
Interlinking | skos check for Apertium RDF ES-AN took 0.28930163383483887s
Interlinking | skos check for Apertium RDF ES-AN took 0.2171013355255127s
Timeliness | dataset update frequency check for Apertium RDF ES-AN took 0.29051756858825684s
Currency | Creation date check for Apertium RDF ES-AN took 0.5718634128570557s
Currency | Modification date check for Apertium RDF ES-AN took 0.5817246437072754s
Rep.Conc. | URIs length for Apertium RDF ES-AN took 58.977887868881226s
Interoperability | New vocabularies check for Apertium RDF ES-AN took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-AN took 0.2912788391113281s
Accuracy | Check Functional Property for Apertium RDF ES-AN took 0.2995927333831787s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-AN took 0.28846263885498047s
Accuracy | Check Empty annotation labels for Apertium RDF ES-AN took 0.8331189155578613s
Accuracy | Check White space in annotation for Apertium RDF ES-AN took 0.01027989387512207s
Accuracy | Check Datatype consistency for Apertium RDF ES-AN took 2.7444114685058594s
Consistency | Disjoint class check for Apertium RDF ES-AN took 0.27291369438171387s
Consistency | Check Misplaced properties for Apertium RDF ES-AN took 4.61398983001709s
Consistency | Misplaced classes for Apertium RDF ES-AN took 8.654135465621948s
Consistency | Check Ontology hijacking for Apertium RDF ES-AN took 44.482683181762695s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-AN took 1.6588609218597412s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-AN took 5.994460821151733s
Conciseness | Check Extensional conciseness for Apertium RDF ES-AN took 3.0697505474090576s
Conciseness | Check Intensional conciseness for Apertium RDF ES-AN took 0.307995080947876s
Security | Sign check for Apertium RDF ES-AN took 0.26769113540649414s
Availability | Check URIs Dereferenciability for Apertium RDF ES-AN took 9.84174919128418s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.49997639656066895s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.021364688873291016s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0008969306945800781s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 5.459785461425781e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-AN took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-es-an took 643.3427803516388s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 0.23909258842468262s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0008549690246582031s
Extra | Recovery of all triples for Apertium RDF ES-AST took 160.7864532470703s
Performance | Total latancy measurement for Apertium RDF ES-AST took 1.2199459075927734s
Amount of data | Number of triples check for Apertium RDF ES-AST took 2.181346893310547s
Interoperability | New terms check for Apertium RDF ES-AST took 3.0325379371643066s
Versatility | Languages check for Apertium RDF ES-AST took 44.43341636657715s
Interpretability | Number of blank nodes check for Apertium RDF ES-AST took 1.078420639038086s
Security | Check HTTPS for Apertium RDF ES-AST took 0.13321709632873535s
Interpretability | RDF structures check for Apertium RDF ES-AST took 0.2995147705078125s
Versatility | Serialization formats check for Apertium RDF ES-AST took 0.3002934455871582s
Availability | RDF dump link check for Apertium RDF ES-AST took 0.2656073570251465s
License | MR license check for Apertium RDF ES-AST took 0.2869601249694824s
License | HR license check for Apertium RDF ES-AST took 0.3766906261444092s
Amount of data | Number of property check for Apertium RDF ES-AST took 0.2991461753845215s
Understandability | Number of label check for Apertium RDF ES-AST took 0.3096179962158203s
Understandability | URI regex check for Apertium RDF ES-AST took 0.558326244354248s
Understandability | Vocabs check for Apertium RDF ES-AST took 0.2971968650817871s
Verifiability | Authors check for Apertium RDF ES-AST took 0.29980039596557617s
Verifiability | Publishers check for Apertium RDF ES-AST took 0.286510705947876s
Performance | Throughput check for Apertium RDF ES-AST took 11.107322931289673s
Amount of data | Check the number of entities for Apertium RDF ES-AST took 3.337860107421875e-05s
Verifiability | Contribs. check for Apertium RDF ES-AST took 0.27722954750061035s
Interlinking | sameAs chians check for Apertium RDF ES-AST took 0.27483057975769043s
Interlinking | skos check for Apertium RDF ES-AST took 0.2760591506958008s
Interlinking | skos check for Apertium RDF ES-AST took 0.23105835914611816s
Timeliness | dataset update frequency check for Apertium RDF ES-AST took 0.294968843460083s
Currency | Creation date check for Apertium RDF ES-AST took 0.5655336380004883s
Currency | Modification date check for Apertium RDF ES-AST took 0.5840034484863281s
Rep.Conc. | URIs length for Apertium RDF ES-AST took 58.409878969192505s
Interoperability | New vocabularies check for Apertium RDF ES-AST took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-AST took 0.3006770610809326s
Accuracy | Check Functional Property for Apertium RDF ES-AST took 0.2846999168395996s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-AST took 0.27440428733825684s
Accuracy | Check Empty annotation labels for Apertium RDF ES-AST took 0.8377573490142822s
Accuracy | Check White space in annotation for Apertium RDF ES-AST took 0.010480403900146484s
Accuracy | Check Datatype consistency for Apertium RDF ES-AST took 2.7188425064086914s
Consistency | Disjoint class check for Apertium RDF ES-AST took 0.2803821563720703s
Consistency | Check Misplaced properties for Apertium RDF ES-AST took 4.655890703201294s
Consistency | Misplaced classes for Apertium RDF ES-AST took 8.58775782585144s
Consistency | Check Ontology hijacking for Apertium RDF ES-AST took 44.735684633255005s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-AST took 1.649045467376709s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-AST took 5.943215608596802s
Conciseness | Check Extensional conciseness for Apertium RDF ES-AST took 3.1070940494537354s
Conciseness | Check Intensional conciseness for Apertium RDF ES-AST took 0.3196742534637451s
Security | Sign check for Apertium RDF ES-AST took 0.2772705554962158s
Availability | Check URIs Dereferenciability for Apertium RDF ES-AST took 9.901357889175415s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.46097826957702637s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.021510601043701172s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 5.173683166503906e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-AST took 2.384185791015625e-06s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 645.3537030220032s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0007677078247070312s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.3758261203765869s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.022047042846679688s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 5.1975250244140625e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 109.18652510643005s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 9.179115295410156e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0007131099700927734s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.3187692165374756s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.02297353744506836s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 5.745887756347656e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 154.73803448677063s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 9.202957153320312e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 28.673080444335938s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.021085262298583984s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 5.507469177246094e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 286.41837882995605s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 9.5367431640625e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0009291172027587891s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.3460543155670166s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02156686782836914s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0010385513305664062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 5.435943603515625e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 213.8525927066803s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 9.298324584960938e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0008826255798339844s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.281158447265625s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.021153688430786133s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 5.8650970458984375e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.33514404296875e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 285.1411201953888s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 0.28563690185546875s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0007236003875732422s
Extra | Recovery of all triples for Apertium RDF EU-ES took 159.61228466033936s
Performance | Total latancy measurement for Apertium RDF EU-ES took 1.1925575733184814s
Amount of data | Number of triples check for Apertium RDF EU-ES took 2.1854145526885986s
Interoperability | New terms check for Apertium RDF EU-ES took 3.11948299407959s
Versatility | Languages check for Apertium RDF EU-ES took 44.41763377189636s
Interpretability | Number of blank nodes check for Apertium RDF EU-ES took 1.3418655395507812s
Security | Check HTTPS for Apertium RDF EU-ES took 0.12575364112854004s
Interpretability | RDF structures check for Apertium RDF EU-ES took 0.28956151008605957s
Versatility | Serialization formats check for Apertium RDF EU-ES took 0.2909829616546631s
Availability | RDF dump link check for Apertium RDF EU-ES took 0.2669854164123535s
License | MR license check for Apertium RDF EU-ES took 0.29071998596191406s
License | HR license check for Apertium RDF EU-ES took 0.37021446228027344s
Amount of data | Number of property check for Apertium RDF EU-ES took 0.28267550468444824s
Understandability | Number of label check for Apertium RDF EU-ES took 0.3352508544921875s
Understandability | URI regex check for Apertium RDF EU-ES took 0.5572471618652344s
Understandability | Vocabs check for Apertium RDF EU-ES took 0.2932584285736084s
Verifiability | Authors check for Apertium RDF EU-ES took 0.29157495498657227s
Verifiability | Publishers check for Apertium RDF EU-ES took 0.27921080589294434s
Performance | Throughput check for Apertium RDF EU-ES took 11.255329370498657s
Amount of data | Check the number of entities for Apertium RDF EU-ES took 8.726119995117188e-05s
Verifiability | Contribs. check for Apertium RDF EU-ES took 0.28702616691589355s
Interlinking | sameAs chians check for Apertium RDF EU-ES took 0.2965271472930908s
Interlinking | skos check for Apertium RDF EU-ES took 0.2871828079223633s
Interlinking | skos check for Apertium RDF EU-ES took 0.23383665084838867s
Timeliness | dataset update frequency check for Apertium RDF EU-ES took 0.28839778900146484s
Currency | Creation date check for Apertium RDF EU-ES took 0.5703997611999512s
Currency | Modification date check for Apertium RDF EU-ES took 0.5711956024169922s
Rep.Conc. | URIs length for Apertium RDF EU-ES took 59.388753175735474s
Interoperability | New vocabularies check for Apertium RDF EU-ES took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EU-ES took 0.30887293815612793s
Accuracy | Check Functional Property for Apertium RDF EU-ES took 0.28498196601867676s
Accuracy | Check Inverse Functional Property for Apertium RDF EU-ES took 0.2786221504211426s
Accuracy | Check Empty annotation labels for Apertium RDF EU-ES took 0.8561849594116211s
Accuracy | Check White space in annotation for Apertium RDF EU-ES took 0.01029515266418457s
Accuracy | Check Datatype consistency for Apertium RDF EU-ES took 2.673149347305298s
Consistency | Disjoint class check for Apertium RDF EU-ES took 0.27884340286254883s
Consistency | Check Misplaced properties for Apertium RDF EU-ES took 4.703807353973389s
Consistency | Misplaced classes for Apertium RDF EU-ES took 8.537200927734375s
Consistency | Check Ontology hijacking for Apertium RDF EU-ES took 45.20895791053772s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EU-ES took 1.6211085319519043s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EU-ES took 5.775009632110596s
Conciseness | Check Extensional conciseness for Apertium RDF EU-ES took 2.925305128097534s
Conciseness | Check Intensional conciseness for Apertium RDF EU-ES took 0.2921462059020996s
Security | Sign check for Apertium RDF EU-ES took 0.2926139831542969s
Availability | Check URIs Dereferenciability for Apertium RDF EU-ES took 10.398513078689575s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.4579946994781494s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.021561622619628906s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EU-ES took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EU-ES took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 635.1721992492676s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 9.393692016601562e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.00080108642578125s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 29.7076895236969s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.021612167358398438s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 5.435943603515625e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 2.2411346435546875e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 252.99659752845764s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 0.29168081283569336s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0006315708160400391s
Extra | Recovery of all triples for Apertium RDF FR-ES took 161.25004386901855s
Performance | Total latancy measurement for Apertium RDF FR-ES took 1.2246334552764893s
Amount of data | Number of triples check for Apertium RDF FR-ES took 2.1683292388916016s
Interoperability | New terms check for Apertium RDF FR-ES took 3.1074187755584717s
Versatility | Languages check for Apertium RDF FR-ES took 44.30715727806091s
Interpretability | Number of blank nodes check for Apertium RDF FR-ES took 1.0847043991088867s
Security | Check HTTPS for Apertium RDF FR-ES took 0.13965201377868652s
Interpretability | RDF structures check for Apertium RDF FR-ES took 0.29236793518066406s
Versatility | Serialization formats check for Apertium RDF FR-ES took 0.284182071685791s
Availability | RDF dump link check for Apertium RDF FR-ES took 0.28952455520629883s
License | MR license check for Apertium RDF FR-ES took 0.26894712448120117s
License | HR license check for Apertium RDF FR-ES took 0.37378931045532227s
Amount of data | Number of property check for Apertium RDF FR-ES took 0.29210662841796875s
Understandability | Number of label check for Apertium RDF FR-ES took 0.3006157875061035s
Understandability | URI regex check for Apertium RDF FR-ES took 0.5648963451385498s
Understandability | Vocabs check for Apertium RDF FR-ES took 0.29755687713623047s
Verifiability | Authors check for Apertium RDF FR-ES took 0.2940800189971924s
Verifiability | Publishers check for Apertium RDF FR-ES took 0.28838372230529785s
Performance | Throughput check for Apertium RDF FR-ES took 11.238338470458984s
Amount of data | Check the number of entities for Apertium RDF FR-ES took 7.581710815429688e-05s
Verifiability | Contribs. check for Apertium RDF FR-ES took 0.28676819801330566s
Interlinking | sameAs chians check for Apertium RDF FR-ES took 0.2674264907836914s
Interlinking | skos check for Apertium RDF FR-ES took 0.2890639305114746s
Interlinking | skos check for Apertium RDF FR-ES took 0.23007535934448242s
Timeliness | dataset update frequency check for Apertium RDF FR-ES took 0.27263712882995605s
Currency | Creation date check for Apertium RDF FR-ES took 0.5536623001098633s
Currency | Modification date check for Apertium RDF FR-ES took 0.5589821338653564s
Rep.Conc. | URIs length for Apertium RDF FR-ES took 59.43986415863037s
Interoperability | New vocabularies check for Apertium RDF FR-ES took 1.2159347534179688e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF FR-ES took 0.27371644973754883s
Accuracy | Check Functional Property for Apertium RDF FR-ES took 0.29430627822875977s
Accuracy | Check Inverse Functional Property for Apertium RDF FR-ES took 0.2648782730102539s
Accuracy | Check Empty annotation labels for Apertium RDF FR-ES took 0.8199384212493896s
Accuracy | Check White space in annotation for Apertium RDF FR-ES took 0.010193347930908203s
Accuracy | Check Datatype consistency for Apertium RDF FR-ES took 2.684030532836914s
Consistency | Disjoint class check for Apertium RDF FR-ES took 0.2699120044708252s
Consistency | Check Misplaced properties for Apertium RDF FR-ES took 4.74898362159729s
Consistency | Misplaced classes for Apertium RDF FR-ES took 8.43924069404602s
Consistency | Check Ontology hijacking for Apertium RDF FR-ES took 44.72166395187378s
Consistency | Check Invalid usage of undefined classes for Apertium RDF FR-ES took 1.6227655410766602s
Consistency | Check Invalid usage of undefined properties for Apertium RDF FR-ES took 5.830200672149658s
Conciseness | Check Extensional conciseness for Apertium RDF FR-ES took 2.9541165828704834s
Conciseness | Check Intensional conciseness for Apertium RDF FR-ES took 0.29691362380981445s
Security | Sign check for Apertium RDF FR-ES took 0.2692544460296631s
Availability | Check URIs Dereferenciability for Apertium RDF FR-ES took 10.571012735366821s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 32.61130428314209s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.021444320678710938s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF FR-ES took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 615.0105555057526s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 9.679794311523438e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0015027523040771484s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 28.163705110549927s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02120065689086914s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0009334087371826172s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 6.103515625e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 159.6246314048767s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 0.2305440902709961s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0006272792816162109s
Extra | Recovery of all triples for Apertium RDF OC-ES took 159.39337301254272s
Performance | Total latancy measurement for Apertium RDF OC-ES took 1.2032275199890137s
Amount of data | Number of triples check for Apertium RDF OC-ES took 2.225520372390747s
Interoperability | New terms check for Apertium RDF OC-ES took 3.141944646835327s
Versatility | Languages check for Apertium RDF OC-ES took 44.81111025810242s
Interpretability | Number of blank nodes check for Apertium RDF OC-ES took 1.0726087093353271s
Security | Check HTTPS for Apertium RDF OC-ES took 0.14520525932312012s
Interpretability | RDF structures check for Apertium RDF OC-ES took 0.2812213897705078s
Versatility | Serialization formats check for Apertium RDF OC-ES took 0.27533936500549316s
Availability | RDF dump link check for Apertium RDF OC-ES took 0.2956876754760742s
License | MR license check for Apertium RDF OC-ES took 0.28789663314819336s
License | HR license check for Apertium RDF OC-ES took 0.3634026050567627s
Amount of data | Number of property check for Apertium RDF OC-ES took 0.27680087089538574s
Understandability | Number of label check for Apertium RDF OC-ES took 0.32581520080566406s
Understandability | URI regex check for Apertium RDF OC-ES took 0.5896642208099365s
Understandability | Vocabs check for Apertium RDF OC-ES took 0.25829076766967773s
Verifiability | Authors check for Apertium RDF OC-ES took 0.2856442928314209s
Verifiability | Publishers check for Apertium RDF OC-ES took 0.28119373321533203s
Performance | Throughput check for Apertium RDF OC-ES took 11.094810485839844s
Amount of data | Check the number of entities for Apertium RDF OC-ES took 7.796287536621094e-05s
Verifiability | Contribs. check for Apertium RDF OC-ES took 0.2890920639038086s
Interlinking | sameAs chians check for Apertium RDF OC-ES took 0.2609739303588867s
Interlinking | skos check for Apertium RDF OC-ES took 0.26873111724853516s
Interlinking | skos check for Apertium RDF OC-ES took 0.21201252937316895s
Timeliness | dataset update frequency check for Apertium RDF OC-ES took 0.29712486267089844s
Currency | Creation date check for Apertium RDF OC-ES took 0.5568325519561768s
Currency | Modification date check for Apertium RDF OC-ES took 0.579911470413208s
Rep.Conc. | URIs length for Apertium RDF OC-ES took 58.17399525642395s
Interoperability | New vocabularies check for Apertium RDF OC-ES took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF OC-ES took 0.2861783504486084s
Accuracy | Check Functional Property for Apertium RDF OC-ES took 0.2674689292907715s
Accuracy | Check Inverse Functional Property for Apertium RDF OC-ES took 0.2814192771911621s
Accuracy | Check Empty annotation labels for Apertium RDF OC-ES took 0.8077483177185059s
Accuracy | Check White space in annotation for Apertium RDF OC-ES took 0.010298490524291992s
Accuracy | Check Datatype consistency for Apertium RDF OC-ES took 2.6668779850006104s
Consistency | Disjoint class check for Apertium RDF OC-ES took 0.2840449810028076s
Consistency | Check Misplaced properties for Apertium RDF OC-ES took 4.721294403076172s
Consistency | Misplaced classes for Apertium RDF OC-ES took 8.594407320022583s
Consistency | Check Ontology hijacking for Apertium RDF OC-ES took 58.99656796455383s
Consistency | Check Invalid usage of undefined classes for Apertium RDF OC-ES took 1.61985182762146s
Consistency | Check Invalid usage of undefined properties for Apertium RDF OC-ES took 5.928995847702026s
Conciseness | Check Extensional conciseness for Apertium RDF OC-ES took 2.9175684452056885s
Conciseness | Check Intensional conciseness for Apertium RDF OC-ES took 0.31290626525878906s
Security | Sign check for Apertium RDF OC-ES took 0.285785436630249s
Availability | Check URIs Dereferenciability for Apertium RDF OC-ES took 9.76928424835205s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.46770691871643066s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020963191986083984s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF OC-ES took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.430511474609375e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 567.2630755901337s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 0.2895948886871338s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006918907165527344s
Extra | Recovery of all triples for Apertium RDF PT-CA took 160.88695096969604s
Performance | Total latancy measurement for Apertium RDF PT-CA took 1.2476375102996826s
Amount of data | Number of triples check for Apertium RDF PT-CA took 2.197268009185791s
Interoperability | New terms check for Apertium RDF PT-CA took 3.0599427223205566s
Versatility | Languages check for Apertium RDF PT-CA took 44.109259605407715s
Interpretability | Number of blank nodes check for Apertium RDF PT-CA took 1.2295536994934082s
Security | Check HTTPS for Apertium RDF PT-CA took 0.14356088638305664s
Interpretability | RDF structures check for Apertium RDF PT-CA took 0.2821059226989746s
Versatility | Serialization formats check for Apertium RDF PT-CA took 0.3079361915588379s
Availability | RDF dump link check for Apertium RDF PT-CA took 0.2760148048400879s
License | MR license check for Apertium RDF PT-CA took 0.2952079772949219s
License | HR license check for Apertium RDF PT-CA took 0.37697553634643555s
Amount of data | Number of property check for Apertium RDF PT-CA took 0.277346134185791s
Understandability | Number of label check for Apertium RDF PT-CA took 0.3239858150482178s
Understandability | URI regex check for Apertium RDF PT-CA took 0.5603692531585693s
Understandability | Vocabs check for Apertium RDF PT-CA took 0.26775360107421875s
Verifiability | Authors check for Apertium RDF PT-CA took 0.29378390312194824s
Verifiability | Publishers check for Apertium RDF PT-CA took 0.2884094715118408s
Performance | Throughput check for Apertium RDF PT-CA took 11.21607518196106s
Amount of data | Check the number of entities for Apertium RDF PT-CA took 0.00011205673217773438s
Verifiability | Contribs. check for Apertium RDF PT-CA took 0.26738929748535156s
Interlinking | sameAs chians check for Apertium RDF PT-CA took 0.29784178733825684s
Interlinking | skos check for Apertium RDF PT-CA took 0.28644895553588867s
Interlinking | skos check for Apertium RDF PT-CA took 0.21547865867614746s
Timeliness | dataset update frequency check for Apertium RDF PT-CA took 0.29569220542907715s
Currency | Creation date check for Apertium RDF PT-CA took 0.5711617469787598s
Currency | Modification date check for Apertium RDF PT-CA took 0.5752360820770264s
Rep.Conc. | URIs length for Apertium RDF PT-CA took 60.01335120201111s
Interoperability | New vocabularies check for Apertium RDF PT-CA took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF PT-CA took 0.28655552864074707s
Accuracy | Check Functional Property for Apertium RDF PT-CA took 0.293959379196167s
Accuracy | Check Inverse Functional Property for Apertium RDF PT-CA took 0.276963472366333s
Accuracy | Check Empty annotation labels for Apertium RDF PT-CA took 0.818572998046875s
Accuracy | Check White space in annotation for Apertium RDF PT-CA took 0.01044321060180664s
Accuracy | Check Datatype consistency for Apertium RDF PT-CA took 2.7457973957061768s
Consistency | Disjoint class check for Apertium RDF PT-CA took 0.2944014072418213s
Consistency | Check Misplaced properties for Apertium RDF PT-CA took 4.607895374298096s
Consistency | Misplaced classes for Apertium RDF PT-CA took 8.669439315795898s
Consistency | Check Ontology hijacking for Apertium RDF PT-CA took 44.63120937347412s
Consistency | Check Invalid usage of undefined classes for Apertium RDF PT-CA took 1.669447898864746s
Consistency | Check Invalid usage of undefined properties for Apertium RDF PT-CA took 5.935273170471191s
Conciseness | Check Extensional conciseness for Apertium RDF PT-CA took 3.0221786499023438s
Conciseness | Check Intensional conciseness for Apertium RDF PT-CA took 0.3207821846008301s
Security | Sign check for Apertium RDF PT-CA took 0.2866852283477783s
Availability | Check URIs Dereferenciability for Apertium RDF PT-CA took 10.242455005645752s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 30.41623067855835s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02214980125427246s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 3.409385681152344e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF PT-CA took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 658.2948451042175s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 0.2706615924835205s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0007121562957763672s
Extra | Recovery of all triples for Apertium RDF PT-GL took 159.80589485168457s
Performance | Total latancy measurement for Apertium RDF PT-GL took 1.2067396640777588s
Amount of data | Number of triples check for Apertium RDF PT-GL took 2.1147005558013916s
Interoperability | New terms check for Apertium RDF PT-GL took 3.052706241607666s
Versatility | Languages check for Apertium RDF PT-GL took 44.0689058303833s
Interpretability | Number of blank nodes check for Apertium RDF PT-GL took 1.2095715999603271s
Security | Check HTTPS for Apertium RDF PT-GL took 0.14528393745422363s
Interpretability | RDF structures check for Apertium RDF PT-GL took 0.29270291328430176s
Versatility | Serialization formats check for Apertium RDF PT-GL took 0.3002650737762451s
Availability | RDF dump link check for Apertium RDF PT-GL took 0.3082311153411865s
License | MR license check for Apertium RDF PT-GL took 0.28125548362731934s
License | HR license check for Apertium RDF PT-GL took 0.3708317279815674s
Amount of data | Number of property check for Apertium RDF PT-GL took 0.27770256996154785s
Understandability | Number of label check for Apertium RDF PT-GL took 0.2954111099243164s
Understandability | URI regex check for Apertium RDF PT-GL took 0.5671002864837646s
Understandability | Vocabs check for Apertium RDF PT-GL took 0.2771120071411133s
Verifiability | Authors check for Apertium RDF PT-GL took 0.2840867042541504s
Verifiability | Publishers check for Apertium RDF PT-GL took 0.2754247188568115s
Performance | Throughput check for Apertium RDF PT-GL took 11.038928508758545s
Amount of data | Check the number of entities for Apertium RDF PT-GL took 3.314018249511719e-05s
Verifiability | Contribs. check for Apertium RDF PT-GL took 0.2768545150756836s
Interlinking | sameAs chians check for Apertium RDF PT-GL took 0.29059362411499023s
Interlinking | skos check for Apertium RDF PT-GL took 0.27265071868896484s
Interlinking | skos check for Apertium RDF PT-GL took 0.20378518104553223s
Timeliness | dataset update frequency check for Apertium RDF PT-GL took 0.28531527519226074s
Currency | Creation date check for Apertium RDF PT-GL took 0.6050488948822021s
Currency | Modification date check for Apertium RDF PT-GL took 0.5722126960754395s
Rep.Conc. | URIs length for Apertium RDF PT-GL took 59.688191413879395s
Interoperability | New vocabularies check for Apertium RDF PT-GL took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF PT-GL took 0.2831246852874756s
Accuracy | Check Functional Property for Apertium RDF PT-GL took 0.2778475284576416s
Accuracy | Check Inverse Functional Property for Apertium RDF PT-GL took 0.27254390716552734s
Accuracy | Check Empty annotation labels for Apertium RDF PT-GL took 0.8226163387298584s
Accuracy | Check White space in annotation for Apertium RDF PT-GL took 0.010314702987670898s
Accuracy | Check Datatype consistency for Apertium RDF PT-GL took 2.7434091567993164s
Consistency | Disjoint class check for Apertium RDF PT-GL took 0.26787424087524414s
Consistency | Check Misplaced properties for Apertium RDF PT-GL took 4.706649541854858s
Consistency | Misplaced classes for Apertium RDF PT-GL took 8.514605045318604s
Consistency | Check Ontology hijacking for Apertium RDF PT-GL took 45.166826248168945s
Consistency | Check Invalid usage of undefined classes for Apertium RDF PT-GL took 1.6448373794555664s
Consistency | Check Invalid usage of undefined properties for Apertium RDF PT-GL took 5.565316438674927s
Conciseness | Check Extensional conciseness for Apertium RDF PT-GL took 3.0606818199157715s
Conciseness | Check Intensional conciseness for Apertium RDF PT-GL took 0.3005838394165039s
Security | Sign check for Apertium RDF PT-GL took 0.2736823558807373s
Availability | Check URIs Dereferenciability for Apertium RDF PT-GL took 9.695597648620605s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.4218592643737793s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.02140331268310547s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0008542537689208984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 6.723403930664062e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF PT-GL took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 595.2241547107697s
Availability | SPARQL endpoint availability check for AragoDBpedia - aragon open data took 0.5715453624725342s
Availability | VoID file availability check for AragoDBpedia - aragon open data took 0.0008339881896972656s
Extra | Recovery of all triples for AragoDBpedia - aragon open data took 2.537627696990967s
Performance | Total latancy measurement for AragoDBpedia - aragon open data took 1.5684208869934082s
Amount of data | Number of triples check for AragoDBpedia - aragon open data took 0.700279712677002s
Interoperability | New terms check for AragoDBpedia - aragon open data took 2.176034688949585s
Versatility | Languages check for AragoDBpedia - aragon open data took 60.43363857269287s
Interpretability | Number of blank nodes check for AragoDBpedia - aragon open data took 3.9642364978790283s
Security | Check HTTPS for AragoDBpedia - aragon open data took 0.2269432544708252s
Interpretability | RDF structures check for AragoDBpedia - aragon open data took 0.6712963581085205s
Versatility | Serialization formats check for AragoDBpedia - aragon open data took 0.8109359741210938s
Availability | RDF dump link check for AragoDBpedia - aragon open data took 0.35056424140930176s
License | MR license check for AragoDBpedia - aragon open data took 0.6631927490234375s
License | HR license check for AragoDBpedia - aragon open data took 6.532046318054199s
Amount of data | Number of property check for AragoDBpedia - aragon open data took 0.36496782302856445s
Understandability | Number of label check for AragoDBpedia - aragon open data took 0.5094358921051025s
Understandability | URI regex check for AragoDBpedia - aragon open data took 0.8269534111022949s
Understandability | Vocabs check for AragoDBpedia - aragon open data took 0.41921544075012207s
Verifiability | Authors check for AragoDBpedia - aragon open data took 0.4662497043609619s
Verifiability | Publishers check for AragoDBpedia - aragon open data took 0.33985447883605957s
Performance | Throughput check for AragoDBpedia - aragon open data took 12.239522457122803s
Amount of data | Check the number of entities for AragoDBpedia - aragon open data took 6.937980651855469e-05s
Verifiability | Contribs. check for AragoDBpedia - aragon open data took 0.43729543685913086s
Interlinking | sameAs chians check for AragoDBpedia - aragon open data took 0.40312933921813965s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.5801131725311279s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.3066709041595459s
Timeliness | dataset update frequency check for AragoDBpedia - aragon open data took 0.41193532943725586s
Currency | Creation date check for AragoDBpedia - aragon open data took 0.9599971771240234s
Currency | Modification date check for AragoDBpedia - aragon open data took 0.34012269973754883s
Rep.Conc. | URIs length for AragoDBpedia - aragon open data took 5.737896680831909s
Interoperability | New vocabularies check for AragoDBpedia - aragon open data took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for AragoDBpedia - aragon open data took 0.32575273513793945s
Accuracy | Check Functional Property for AragoDBpedia - aragon open data took 0.409959077835083s
Accuracy | Check Inverse Functional Property for AragoDBpedia - aragon open data took 0.40262603759765625s
Accuracy | Check Empty annotation labels for AragoDBpedia - aragon open data took 1.2360954284667969s
Accuracy | Check White space in annotation for AragoDBpedia - aragon open data took 0.02998495101928711s
Accuracy | Check Datatype consistency for AragoDBpedia - aragon open data took 0.03016519546508789s
Consistency | Disjoint class check for AragoDBpedia - aragon open data took 0.33365726470947266s
Consistency | Check Misplaced properties for AragoDBpedia - aragon open data took 4.164871454238892s
Consistency | Misplaced classes for AragoDBpedia - aragon open data took 0.5170259475708008s
Consistency | Check Ontology hijacking for AragoDBpedia - aragon open data took 2.5852608680725098s
Consistency | Check Invalid usage of undefined classes for AragoDBpedia - aragon open data took 1.5626442432403564s
Consistency | Check Invalid usage of undefined properties for AragoDBpedia - aragon open data took 5.33110237121582s
Conciseness | Check Extensional conciseness for AragoDBpedia - aragon open data took 0.035367488861083984s
Conciseness | Check Intensional conciseness for AragoDBpedia - aragon open data took 0.49932265281677246s
Security | Sign check for AragoDBpedia - aragon open data took 0.6193134784698486s
Availability | Check URIs Dereferenciability for AragoDBpedia - aragon open data took 2746.4481887817383s
Completeness | Calculation of interlinking completeness for AragoDBpedia - aragon open data took 32.83576965332031s
Reputation | Calculation of the PageRank for AragoDBpedia - aragon open data took 0.021609783172607422s
Interlinking | Calculation of Degree of Connection for AragoDBpedia - aragon open data took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for AragoDBpedia - aragon open data took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for AragoDBpedia - aragon open data took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBpedia - aragon open data took 1.6689300537109375e-06s
Believability | Calculation of trust value for AragoDBpedia - aragon open data took 9.059906005859375e-06s
INFO | --- Analysis for aragodbpedia took 3097.1777188777924s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.12788200378418s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0008435249328613281s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 27.639064073562622s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.02122807502746582s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.626678466796875e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for archiveshub-linkeddata took 207.22737193107605s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 5.046097040176392s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 29.10321307182312s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.02132415771484375s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 4.363059997558594e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 7.867813110351562e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 238.14459991455078s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.845501661300659s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.31708693504333496s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.021157264709472656s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.696846008300781e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.1682510375976562e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 198.07555198669434s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.38690185546875e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0008370876312255859s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 32.96190810203552s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.021273374557495117s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00011086463928222656s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.059906005859375e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 189.10866451263428s
Availability | SPARQL endpoint availability check for Arthroscopy community took 9.1552734375e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 29.866937398910522s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.02134108543395996s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00013494491577148438s
Believability | Calculation of trust value for Arthroscopy community took 1.5020370483398438e-05s
INFO | --- Analysis for arthroscopy took 130.68138909339905s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.9034543037414551s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0008413791656494141s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 39.44423818588257s
Performance | Total latancy measurement for Wikidata entry for Art × Science International took 0.7283022403717041s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 60.38712811470032s
Interoperability | New terms check for Wikidata entry for Art × Science International took 2.0659914016723633s
Versatility | Languages check for Wikidata entry for Art × Science International took 65.16665363311768s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 0.21486783027648926s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.19508695602416992s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.1967780590057373s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.21046042442321777s
License | MR license check for Wikidata entry for Art × Science International took 0.2982611656188965s
License | HR license check for Wikidata entry for Art × Science International took 65.15846014022827s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.5170729160308838s
Understandability | Number of label check for Wikidata entry for Art × Science International took 65.18127417564392s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.40976595878601074s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.20615553855895996s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.18326115608215332s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.19217181205749512s
Performance | Throughput check for Wikidata entry for Art × Science International took 11.155681610107422s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 7.700920104980469e-05s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.22992801666259766s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 35.819892168045044s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.2322981357574463s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.2069549560546875s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.19484400749206543s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.40851879119873047s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.6856343746185303s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 45.83401966094971s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 1.1920928955078125e-05s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.17922163009643555s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.674309730529785s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.19517183303833008s
Consistency | Check Misplaced properties for Wikidata entry for Art × Science International took 16.063538551330566s
Consistency | Misplaced classes for Wikidata entry for Art × Science International took 9.718471765518188s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 38.26880168914795s
Consistency | Check Invalid usage of undefined classes for Wikidata entry for Art × Science International took 1.5600011348724365s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 3.80452036857605s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.845052719116211s
Conciseness | Check Intensional conciseness for Wikidata entry for Art × Science International took 1.654057264328003s
Security | Sign check for Wikidata entry for Art × Science International took 0.1714155673980713s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 9.077164649963379s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 28.737900257110596s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.021867036819458008s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.52587890625e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 2.1457672119140625e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 1.1682510375976562e-05s
INFO | --- Analysis for artxscienceinternational-wikidata took 1080.3607914447784s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.1918222904205322s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.33046555519104004s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020801305770874023s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.796287536621094e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.2159347534179688e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 170.32532954216003s
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.1827476024627686s
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.00042700767517089844s
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.3503432273864746s
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.023235559463500977s
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.33514404296875e-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.0007355213165283203s
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 9.107589721679688e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 132.0940454006195s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.169771671295166s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.32818031311035156s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020994901657104492s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.250640869140625e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 75.66351294517517s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.1726253032684326s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0007419586181640625s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 30.33907985687256s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.02149677276611328s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.982948303222656e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.2159347534179688e-05s
INFO | --- Analysis for ASCDC-CRB took 168.11207580566406s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.1893680095672607s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.38680076599121094s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.02215719223022461s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.918212890625e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.2649765014648438e-05s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 132.73403549194336s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.188516855239868s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.3378334045410156s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.023702383041381836s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 4.696846008300781e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.6927719116210938e-05s
INFO | --- Analysis for ASCDC-DQOT took 102.72278952598572s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.195221185684204s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0008335113525390625s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.3125183582305908s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.021338701248168945s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 9.012222290039062e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.1444091796875e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 130.26454734802246s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 2.905895948410034s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 28.282291650772095s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.023360252380371094s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0017578601837158203s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 0.00016164779663085938s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 160.80410313606262s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.206883430480957s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006833076477050781s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 25.691974878311157s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.02115941047668457s
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.2636184692382812e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0008845329284667969s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 6.413459777832031e-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.1444091796875e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 170.60955476760864s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.175156831741333s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 28.71210479736328s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.021153926849365234s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 6.461143493652344e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.2636184692382812e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 151.98043847084045s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.4915053844451904s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 26.9652042388916s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020859956741333008s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 5.078315734863281e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 125.52076363563538s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.190002202987671s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 24.70863652229309s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020982980728149414s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 8.225440979003906e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.5974044799804688e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 141.54131388664246s
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.190948247909546s
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.0006971359252929688s
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 28.30284309387207s
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.022113561630249023s
Interlinking | Calculation of Degree of Connection for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0007522106170654297s
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 9.322166442871094e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.239776611328125e-05s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 200.98767066001892s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.663029909133911s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0007014274597167969s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 24.60978627204895s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020946979522705078s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.839897155761719e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC_-_DNB took 152.46571850776672s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.792213439941406e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 32.10794281959534s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.02189779281616211s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 7.271766662597656e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.6689300537109375e-05s
INFO | --- Analysis for asit took 124.34679460525513s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.482269287109375e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.31267547607421875s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.021147727966308594s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 2.86102294921875e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 4.744529724121094e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.2159347534179688e-05s
INFO | --- Analysis for asjp took 120.94391441345215s
Availability | SPARQL endpoint availability check for ASN:US took 2.861829996109009s
Availability | VoID file availability check for ASN:US took 0.00031948089599609375s
Completeness | Calculation of interlinking completeness for ASN:US took 0.31620001792907715s
Reputation | Calculation of the PageRank for ASN:US took 0.02203202247619629s
Interlinking | Calculation of Degree of Connection for ASN:US took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for ASN:US took 7.867813110351562e-05s
Believability | Calculation of trust value for ASN:US took 1.0251998901367188e-05s
INFO | --- Analysis for asn-us took 190.8320438861847s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 9.322166442871094e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006551742553710938s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.3563265800476074s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.021080970764160156s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.361701965332031e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 9.298324584960938e-06s
INFO | --- Analysis for aspire-mmu took 58.919559478759766s
Availability | SPARQL endpoint availability check for associations took 4.506111145019531e-05s
Availability | VoID file availability check for associations took 0.000797271728515625s
Completeness | Calculation of interlinking completeness for associations took 30.249674081802368s
Reputation | Calculation of the PageRank for associations took 0.021359682083129883s
Interlinking | Calculation of Degree of Connection for associations took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for associations took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for associations took 7.677078247070312e-05s
Believability | Calculation of trust value for associations took 1.2159347534179688e-05s
INFO | --- Analysis for associations took 148.63168144226074s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.7206878662109375e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.32391810417175293s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.02096247673034668s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 3.218650817871094e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 1.2636184692382812e-05s
INFO | --- Analysis for atc-publikovan--s-kl took 179.82517457008362s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.458427429199219e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0009410381317138672s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 26.11033535003662s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.021069765090942383s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 9.322166442871094e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.5974044799804688e-05s
INFO | --- Analysis for athelia-rfid took 199.7594437599182s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 5.088624715805054s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 29.148497819900513s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.021105289459228516s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 4.00543212890625e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 1.239776611328125e-05s
INFO | --- Analysis for aueb-linked-open-data took 200.27176237106323s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.5594875812530518s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 27.713590621948242s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.02093195915222168s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.9604644775390625e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.0967254638671875e-05s
INFO | --- Analysis for AugustiniConfessiones took 171.2310769557953s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.47306394577026367s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0008051395416259766s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 29.562296390533447s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02118206024169922s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 0.00010204315185546875s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.3589859008789062e-05s
INFO | --- Analysis for austrian_ski_racers took 142.0741994380951s
Availability | SPARQL endpoint availability check for AVsOnto took 4.982948303222656e-05s
Availability | VoID file availability check for AVsOnto took 0.0007569789886474609s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.31240367889404297s
Reputation | Calculation of the PageRank for AVsOnto took 0.022101402282714844s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0008263587951660156s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.647804260253906e-05s
Believability | Calculation of trust value for AVsOnto took 1.2159347534179688e-05s
INFO | --- Analysis for AVsOnto took 191.00589871406555s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3505.3478643894196s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0006501674652099609s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 198.8882553577423s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 84.48946595191956s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0878174304962s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.09606766700745s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1053113937378s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0350749492645s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0200672149658s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0646412372589s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0709025859833s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0859684944153s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1047189235687s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0257041454315s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 600.1325964927673s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10419154167175s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0320734977722s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.08403396606445s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.00010919570922851562s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1049454212189s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0654385089874s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0989422798157s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10027503967285s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10521841049194s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 600.1242742538452s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 569.2853853702545s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1052.840983390808s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1233222484588623s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 13.977304935455322s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.234466552734375s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.9487175941467285s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1315479278564453s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1989161968231s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 406.3167154788971s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.988335132598877s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.6593301296234s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.877424478530884s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.18173670768737793s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.218750238418579s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.8736553192138672s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021854877471923828s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.510185241699219e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.1920928955078125e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.0251998901367188e-05s
INFO | --- Analysis for b3kat took 15480.356616258621s
Availability | SPARQL endpoint availability check for BabelNet took 0.5946993827819824s
Availability | VoID file availability check for BabelNet took 0.0007877349853515625s
Completeness | Calculation of interlinking completeness for BabelNet took 0.3015787601470947s
Reputation | Calculation of the PageRank for BabelNet took 0.021359920501708984s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.000171661376953125s
Believability | Calculation of trust value for BabelNet took 1.239776611328125e-05s
INFO | --- Analysis for babelnet took 146.0532796382904s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.792213439941406e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 34.12937617301941s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.022166967391967773s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 4.696846008300781e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.52587890625e-05s
INFO | --- Analysis for Bacevicius.lt took 206.5277168750763s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.503054141998291s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 24.576465606689453s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.021979808807373047s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.696846008300781e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.2159347534179688e-05s
INFO | --- Analysis for bag took 173.2401032447815s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 1.401118516921997s
Availability | VoID file availability check for 红色经典歌曲 took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 31.022542476654053s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02107405662536621s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.552436828613281e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.7881393432617188e-05s
INFO | --- Analysis for baixue took 124.75186347961426s
Availability | SPARQL endpoint availability check for baixue composer took 9.083747863769531e-05s
Availability | VoID file availability check for baixue composer took 0.00036978721618652344s
Completeness | Calculation of interlinking completeness for baixue composer took 26.543555736541748s
Reputation | Calculation of the PageRank for baixue composer took 0.021195173263549805s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.4332275390625e-05s
Believability | Calculation of trust value for baixue composer took 1.1444091796875e-05s
INFO | --- Analysis for baixue_composer took 56.61690974235535s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.00011801719665527344s
Availability | VoID file availability check for 红色经典歌曲 took 0.0007691383361816406s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.31231164932250977s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.021078824996948242s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.981590270996094e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.2159347534179688e-05s
INFO | --- Analysis for baixue_imagery took 146.77426481246948s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 6.413459777832031e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0007007122039794922s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.3409459590911865s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02122664451599121s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 4.029273986816406e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.2159347534179688e-05s
INFO | --- Analysis for baixue_imagery1 took 166.06016039848328s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 8.749961853027344e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 31.131362676620483s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.02119898796081543s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.363059997558594e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.2874603271484375e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 142.8422727584839s
Availability | SPARQL endpoint availability check for BBC Music took 0.5188720226287842s
Availability | VoID file availability check for BBC Music took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for BBC Music took 29.48661470413208s
Reputation | Calculation of the PageRank for BBC Music took 0.020943880081176758s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00012636184692382812s
Believability | Calculation of trust value for BBC Music took 1.1920928955078125e-05s
INFO | --- Analysis for bbc-music took 174.55345916748047s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.3631312847137451s
Availability | VoID file availability check for BBC Programmes took 0.00038170814514160156s
Completeness | Calculation of interlinking completeness for BBC Programmes took 29.150240421295166s
Reputation | Calculation of the PageRank for BBC Programmes took 0.023157119750976562s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0008788108825683594s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.0001399517059326172s
Believability | Calculation of trust value for BBC Programmes took 1.1920928955078125e-05s
INFO | --- Analysis for bbc-programmes took 208.61759567260742s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.34592700004577637s
Availability | VoID file availability check for BBC Wildlife Finder took 0.00035452842712402344s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 22.779003143310547s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.021213054656982422s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00011157989501953125s
Believability | Calculation of trust value for BBC Wildlife Finder took 1.1920928955078125e-05s
INFO | --- Analysis for bbc-wildlife-finder took 191.71384119987488s
Availability | SPARQL endpoint availability check for BBOP took 4.38690185546875e-05s
Availability | VoID file availability check for BBOP took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for BBOP took 25.96742033958435s
Reputation | Calculation of the PageRank for BBOP took 0.02281498908996582s
Interlinking | Calculation of Degree of Connection for BBOP took 2.288818359375e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0011403560638427734s
Interlinking | Calculation of Clustering coefficient for BBOP took 5.054473876953125e-05s
Believability | Calculation of trust value for BBOP took 1.1920928955078125e-05s
INFO | --- Analysis for bbop-selected took 130.90092086791992s
Availability | SPARQL endpoint availability check for Bdgp took 3.6517207622528076s
Availability | VoID file availability check for Bdgp took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Bdgp took 29.339255332946777s
Reputation | Calculation of the PageRank for Bdgp took 0.021088600158691406s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0009436607360839844s
Interlinking | Calculation of Clustering coefficient for Bdgp took 5.8650970458984375e-05s
Believability | Calculation of trust value for Bdgp took 1.2636184692382812e-05s
INFO | --- Analysis for bdgp took 66.65121793746948s
Availability | SPARQL endpoint availability check for Bendev Junior took 0.00012063980102539062s
Availability | VoID file availability check for Bendev Junior took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.2991635799407959s
Reputation | Calculation of the PageRank for Bendev Junior took 0.022330522537231445s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.409385681152344e-05s
Believability | Calculation of trust value for Bendev Junior took 7.867813110351562e-06s
INFO | --- Analysis for bendevoficial took 83.97600603103638s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 6.531139850616455s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.31479525566101074s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.021433353424072266s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.295608520507812e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 5.245208740234375e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 69.28100371360779s
Availability | SPARQL endpoint availability check for berlios took 5.984306335449219e-05s
Availability | VoID file availability check for berlios took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for berlios took 0.3080558776855469s
Reputation | Calculation of the PageRank for berlios took 0.0209505558013916s
Interlinking | Calculation of Degree of Connection for berlios took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for berlios took 9.226799011230469e-05s
Believability | Calculation of trust value for berlios took 7.62939453125e-06s
INFO | --- Analysis for berlios took 83.44481420516968s
Availability | SPARQL endpoint availability check for Between Our Worlds took 9.083747863769531e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 33.38297438621521s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.02091073989868164s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0008261203765869141s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 7.963180541992188e-05s
Believability | Calculation of trust value for Between Our Worlds took 8.344650268554688e-06s
INFO | --- Analysis for betweenourworlds took 143.54647064208984s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.10817742347717285s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 21.63523530960083s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.021125078201293945s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.202957153320312e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for bfs-linked-data took 204.72967100143433s
Availability | SPARQL endpoint availability check for BibBase took 0.07427835464477539s
Availability | VoID file availability check for BibBase took 0.00034737586975097656s
Completeness | Calculation of interlinking completeness for BibBase took 30.161457538604736s
Reputation | Calculation of the PageRank for BibBase took 0.02175283432006836s
Interlinking | Calculation of Degree of Connection for BibBase took 2.7418136596679688e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007987022399902344s
Interlinking | Calculation of Clustering coefficient for BibBase took 0.00011444091796875s
Believability | Calculation of trust value for BibBase took 1.239776611328125e-05s
INFO | --- Analysis for bibbase took 108.69034433364868s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 9.059906005859375e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0007777214050292969s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 30.304147481918335s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.02361011505126953s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0012454986572265625s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00014066696166992188s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.2636184692382812e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 182.90734601020813s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 8.153915405273438e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.302976131439209s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.02162337303161621s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00011038780212402344s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.2159347534179688e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 107.01318407058716s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.00032258033752441406s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 27.400407791137695s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.022144079208374023s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.457069396972656e-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 159.6918981075287s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 9.560585021972656e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.2908053398132324s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.0212094783782959s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 4.673004150390625e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 7.867813110351562e-06s
INFO | --- Analysis for BibSonomy took 120.78083539009094s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.9591064453125e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0007796287536621094s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 30.56729507446289s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.0213472843170166s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0009641647338867188s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.9577484130859375e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 7.152557373046875e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 139.93705034255981s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.935264587402344e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.31327295303344727s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.021036624908447266s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 0.00014472007751464844s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.3113021850585938e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 131.51658701896667s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.8874170780181885s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0007505416870117188s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 20.210817098617554s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5361032485961914s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 45.67141771316528s
Interoperability | New terms check for Bio2RDF::Affymetrix took 43.229968309402466s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.13061332702637s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.14983272552490234s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.9102823734283447s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.20619797706604004s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 2.2203280925750732s
License | MR license check for Bio2RDF::Affymetrix took 0.36923933029174805s
License | HR license check for Bio2RDF::Affymetrix took 60.090149879455566s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.13234400749206543s
Understandability | Number of label check for Bio2RDF::Affymetrix took 10.199016571044922s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.36572790145874023s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.13352632522583008s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.14417767524719238s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.13300514221191406s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.645179986953735s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 80.52007222175598s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.14517664909362793s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.2560575008392334s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.8728213310241699s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.19064116477966309s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.12511730194091797s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.26494908332824707s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.23979473114013672s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 109.25273847579956s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 22.02967071533203s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.3064851760864258s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.15193772315979004s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.12520909309387207s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 6.714089393615723s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.9000678062438965s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6844649314880371s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.3362421989440918s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 65.08587908744812s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.6765549182891846s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.259833335876465s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.371422529220581s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.46172094345093s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7148125171661377s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.3174891471862793s
Security | Sign check for Bio2RDF::Affymetrix took 0.12116622924804688s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 11.018343925476074s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.39806556701660156s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.021048784255981445s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00012230873107910156s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 20.435611486434937s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1173.1054582595825s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.5073676109313965s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.00047278404235839844s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 18.797679662704468s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.271575689315796s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 46.081157207489014s
Interoperability | New terms check for Bio2RDF::Biomodels took 42.72862005233765s
Versatility | Languages check for Bio2RDF::Biomodels took 60.251455783843994s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.25149989128112793s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.157318115234375s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.9596652984619141s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.32305192947387695s
Availability | RDF dump link check for Bio2RDF::Biomodels took 2.3214073181152344s
License | MR license check for Bio2RDF::Biomodels took 0.49631547927856445s
License | HR license check for Bio2RDF::Biomodels took 60.250070333480835s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.25668787956237793s
Understandability | Number of label check for Bio2RDF::Biomodels took 9.617899656295776s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5929598808288574s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2673184871673584s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.26473379135131836s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.26859211921691895s
Performance | Throughput check for Bio2RDF::Biomodels took 10.968051671981812s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 80.60559225082397s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.27266407012939453s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.3904600143432617s
Interlinking | skos check for Bio2RDF::Biomodels took 0.775738000869751s
Interlinking | skos check for Bio2RDF::Biomodels took 0.3565363883972168s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.28433966636657715s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5145750045776367s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5033342838287354s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 111.01716566085815s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 15.059251308441162s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.43182826042175293s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.28206682205200195s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.2808248996734619s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 7.1147215366363525s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.8997249603271484s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6720209121704102s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.48935556411743164s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.76716423034668s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.8364219665527344s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.814634561538696s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.3890621662139893s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.63431000709534s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7179980278015137s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.47126150131225586s
Security | Sign check for Bio2RDF::Biomodels took 0.28297996520996094s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 9.803528070449829s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 27.645320177078247s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.02092432975769043s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011849403381347656s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 36.357901096343994s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.4781951904296875e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1226.9731352329254s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.47246861457824707s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0008978843688964844s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 19.51800227165222s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2268812656402588s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 45.376864194869995s
Interoperability | New terms check for Bio2RDF::Bioportal took 41.92134690284729s
Versatility | Languages check for Bio2RDF::Bioportal took 60.23779630661011s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2684202194213867s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.14651012420654297s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.8094635009765625s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.3378453254699707s
Availability | RDF dump link check for Bio2RDF::Bioportal took 2.3656561374664307s
License | MR license check for Bio2RDF::Bioportal took 0.5391185283660889s
License | HR license check for Bio2RDF::Bioportal took 60.2300865650177s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2770655155181885s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.55417013168335s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.6205518245697021s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.27277612686157227s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.2722141742706299s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.24756956100463867s
Performance | Throughput check for Bio2RDF::Bioportal took 11.358788251876831s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 84.66954827308655s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.2712883949279785s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.42734718322753906s
Interlinking | skos check for Bio2RDF::Bioportal took 1.1740937232971191s
Interlinking | skos check for Bio2RDF::Bioportal took 0.34175753593444824s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.25635290145874023s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5152177810668945s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5052111148834229s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 109.47796487808228s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 11.452336311340332s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.4290168285369873s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.27260303497314453s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.2812049388885498s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 6.981794834136963s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8975474834442139s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6934902667999268s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.5180349349975586s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.84414577484131s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.668548345565796s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.683461904525757s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.3668897151947021s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.62497878074646s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.724360466003418s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.42162656784057617s
Security | Sign check for Bio2RDF::Bioportal took 0.2820572853088379s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 9.996952772140503s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 30.39525318145752s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.020832061767578125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004258155822753906s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 11.663594722747803s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1238.243880033493s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.15123605728149414s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.31697797775268555s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.02131795883178711s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 6.914138793945312e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-chembl took 42.060317277908325s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.48240184783935547s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0004096031188964844s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 18.697100400924683s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.24318265914917s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 46.80298829078674s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 43.47229218482971s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.23820185661316s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.26911163330078125s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.15813970565795898s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.8096356391906738s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.33093929290771484s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 2.12038516998291s
License | MR license check for Bio2RDF::Clinicaltrials took 0.499265193939209s
License | HR license check for Bio2RDF::Clinicaltrials took 60.25462889671326s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.28098607063293457s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.092119932174683s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.57851243019104s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.2501802444458008s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2558467388153076s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.253939151763916s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 10.786743402481079s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 80.91905522346497s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.2657289505004883s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.3508453369140625s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.7011415958404541s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3462638854980469s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.27523350715637207s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5158865451812744s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.533658504486084s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 110.55286002159119s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 12.731106281280518s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.4094531536102295s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.27295899391174316s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.27896857261657715s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 6.89159631729126s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.897249698638916s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6831095218658447s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.4099597930908203s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.1298201084137s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.611785411834717s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.841232538223267s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3889577388763428s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.629605770111084s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7151205539703369s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.4391148090362549s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.26846909523010254s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 10.791219711303711s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.5703616142272949s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020885705947875977s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.888938903808594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 12.254640102386475s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1176.4737911224365s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.46903443336486816s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0007276535034179688s
Extra | Recovery of all triples for Bio2RDF::Ctd took 18.284655570983887s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2526907920837402s
Amount of data | Number of triples check for Bio2RDF::Ctd took 45.6582396030426s
Interoperability | New terms check for Bio2RDF::Ctd took 41.5048348903656s
Versatility | Languages check for Bio2RDF::Ctd took 60.24410581588745s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.2815673351287842s
Security | Check HTTPS for Bio2RDF::Ctd took 0.14616680145263672s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.9105525016784668s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.3267195224761963s
Availability | RDF dump link check for Bio2RDF::Ctd took 2.3877639770507812s
License | MR license check for Bio2RDF::Ctd took 0.47899961471557617s
License | HR license check for Bio2RDF::Ctd took 60.23051714897156s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.28942203521728516s
Understandability | Number of label check for Bio2RDF::Ctd took 10.064057350158691s
Understandability | URI regex check for Bio2RDF::Ctd took 0.6007287502288818s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.24893403053283691s
Verifiability | Authors check for Bio2RDF::Ctd took 0.28357505798339844s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.25077366828918457s
Performance | Throughput check for Bio2RDF::Ctd took 10.841477155685425s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 80.62825202941895s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.275745153427124s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.37499332427978516s
Interlinking | skos check for Bio2RDF::Ctd took 0.7219185829162598s
Interlinking | skos check for Bio2RDF::Ctd took 0.3599727153778076s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.28257274627685547s
Currency | Creation date check for Bio2RDF::Ctd took 0.5059936046600342s
Currency | Modification date check for Bio2RDF::Ctd took 0.5350496768951416s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 111.70890998840332s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 12.264284372329712s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.45735645294189453s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.28008222579956055s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.2844212055206299s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 7.004454612731934s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.9122834205627441s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.673799991607666s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.39606523513793945s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.38425946235657s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.5847349166870117s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.631908416748047s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3919239044189453s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.63118886947632s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7257814407348633s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.4228172302246094s
Security | Sign check for Bio2RDF::Ctd took 0.2598989009857178s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 10.291219472885132s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 22.92003035545349s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.021744251251220703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0009949207305908203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 8.606910705566406e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 12.292152643203735s
Believability | Calculation of trust value for Bio2RDF::Ctd took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-ctd took 1225.3614807128906s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 0.00010371208190917969s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 27.555100440979004s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.021554231643676758s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 6.127357482910156e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-dataset took 200.73480939865112s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.6737048625946045s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0006413459777832031s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 20.493698358535767s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2808332443237305s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 46.13875484466553s
Interoperability | New terms check for Bio2RDF::Dbsnp took 41.78953313827515s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.25799584388733s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.2505362033843994s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.1676478385925293s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 1.1871514320373535s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.3397970199584961s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 2.2945868968963623s
License | MR license check for Bio2RDF::Dbsnp took 0.5097188949584961s
License | HR license check for Bio2RDF::Dbsnp took 60.26387906074524s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.2571113109588623s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.176707983016968s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.6267366409301758s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.244232177734375s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.26439356803894043s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.2608799934387207s
Performance | Throughput check for Bio2RDF::Dbsnp took 11.18383502960205s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 80.88137865066528s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.6192517280578613s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.3614237308502197s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.9392595291137695s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.36115312576293945s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.27089548110961914s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5287351608276367s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.521904468536377s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 108.92093110084534s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 12.854776859283447s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.40696287155151367s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.3037717342376709s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.2937135696411133s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 7.283067226409912s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.9016056060791016s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6766777038574219s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.4364595413208008s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.48912310600281s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.4515137672424316s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 7.5385730266571045s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.3767318725585938s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.631125688552856s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7220618724822998s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.4597656726837158s
Security | Sign check for Bio2RDF::Dbsnp took 0.3172626495361328s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 9.868514776229858s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 29.24640464782715s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.02102208137512207s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.033348083496094e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 14.28274130821228s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 1206.9257276058197s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.4716200828552246s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0007240772247314453s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 18.812870979309082s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2252976894378662s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 46.311028242111206s
Interoperability | New terms check for Bio2RDF::Drugbank took 45.21999955177307s
Versatility | Languages check for Bio2RDF::Drugbank took 60.225117683410645s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.27193713188171387s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.15456223487854004s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 1.0853254795074463s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3175468444824219s
Availability | RDF dump link check for Bio2RDF::Drugbank took 2.225862979888916s
License | MR license check for Bio2RDF::Drugbank took 0.4588603973388672s
License | HR license check for Bio2RDF::Drugbank took 60.25413131713867s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.31728696823120117s
Understandability | Number of label check for Bio2RDF::Drugbank took 10.149672746658325s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5811657905578613s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.27349162101745605s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.2833380699157715s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.27132630348205566s
Performance | Throughput check for Bio2RDF::Drugbank took 11.000021696090698s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 80.57202529907227s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.5779969692230225s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.3589015007019043s
Interlinking | skos check for Bio2RDF::Drugbank took 0.790088415145874s
Interlinking | skos check for Bio2RDF::Drugbank took 0.35509324073791504s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.25537586212158203s
Currency | Creation date check for Bio2RDF::Drugbank took 0.48937153816223145s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5606424808502197s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 109.97607827186584s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 13.49808120727539s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.43950629234313965s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.3017292022705078s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.2880737781524658s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 7.182282447814941s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.9232773780822754s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.674644947052002s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.47621893882751465s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.47726249694824s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.4776430130004883s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.640845060348511s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.391822099685669s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.64493656158447s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7261693477630615s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.5240240097045898s
Security | Sign check for Bio2RDF::Drugbank took 0.27876877784729004s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 11.13532543182373s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 30.415104627609253s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020787715911865234s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00011849403381347656s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 13.655950546264648s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-drugbank took 1229.6321358680725s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.5082950592041016s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006797313690185547s
Extra | Recovery of all triples for Bio2RDF::Genage took 20.941648244857788s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2865443229675293s
Amount of data | Number of triples check for Bio2RDF::Genage took 45.897207498550415s
Interoperability | New terms check for Bio2RDF::Genage took 41.53954219818115s
Versatility | Languages check for Bio2RDF::Genage took 60.25445914268494s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.26278185844421387s
Security | Check HTTPS for Bio2RDF::Genage took 0.1471865177154541s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.7291843891143799s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.3408663272857666s
Availability | RDF dump link check for Bio2RDF::Genage took 2.4965174198150635s
License | MR license check for Bio2RDF::Genage took 0.5036237239837646s
License | HR license check for Bio2RDF::Genage took 60.24756622314453s
Amount of data | Number of property check for Bio2RDF::Genage took 0.2519264221191406s
Understandability | Number of label check for Bio2RDF::Genage took 9.80828595161438s
Understandability | URI regex check for Bio2RDF::Genage took 0.58097243309021s
Understandability | Vocabs check for Bio2RDF::Genage took 0.2501339912414551s
Verifiability | Authors check for Bio2RDF::Genage took 0.24826407432556152s
Verifiability | Publishers check for Bio2RDF::Genage took 0.24576187133789062s
Performance | Throughput check for Bio2RDF::Genage took 11.210652351379395s
Amount of data | Check the number of entities for Bio2RDF::Genage took 84.20153641700745s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.2866642475128174s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.33496642112731934s
Interlinking | skos check for Bio2RDF::Genage took 0.6441080570220947s
Interlinking | skos check for Bio2RDF::Genage took 0.3480641841888428s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2557251453399658s
Currency | Creation date check for Bio2RDF::Genage took 0.5233800411224365s
Currency | Modification date check for Bio2RDF::Genage took 0.5286695957183838s
Rep.Conc. | URIs length for Bio2RDF::Genage took 109.54547071456909s
Interoperability | New vocabularies check for Bio2RDF::Genage took 13.083530187606812s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.4378941059112549s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.2796041965484619s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.2880434989929199s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.263724088668823s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8958485126495361s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6816513538360596s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.459850549697876s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 64.9522488117218s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.6565299034118652s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.25856614112854s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.3726987838745117s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.60300374031067s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7302625179290771s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.43839454650878906s
Security | Sign check for Bio2RDF::Genage took 0.27555012702941895s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 9.717370986938477s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.48120784759521484s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.021332979202270508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 7.843971252441406e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 12.611079454421997s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-genage took 1176.6126201152802s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 0.1416926383972168s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 30.18571138381958s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.021320581436157227s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 8.988380432128906e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-genbank took 215.65613460540771s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.696608304977417s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0007176399230957031s
Extra | Recovery of all triples for Bio2RDF::Gendr took 18.694040060043335s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2393901348114014s
Amount of data | Number of triples check for Bio2RDF::Gendr took 44.96480107307434s
Interoperability | New terms check for Bio2RDF::Gendr took 41.60131907463074s
Versatility | Languages check for Bio2RDF::Gendr took 60.24760580062866s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.2472527027130127s
Security | Check HTTPS for Bio2RDF::Gendr took 0.1651906967163086s
Interpretability | RDF structures check for Bio2RDF::Gendr took 1.0174689292907715s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.34199094772338867s
Availability | RDF dump link check for Bio2RDF::Gendr took 2.46095609664917s
License | MR license check for Bio2RDF::Gendr took 0.4931607246398926s
License | HR license check for Bio2RDF::Gendr took 60.249417781829834s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.25824451446533203s
Understandability | Number of label check for Bio2RDF::Gendr took 10.08995008468628s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5744738578796387s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.2698695659637451s
Verifiability | Authors check for Bio2RDF::Gendr took 0.2621026039123535s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2735323905944824s
Performance | Throughput check for Bio2RDF::Gendr took 11.801752805709839s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 83.36934041976929s
Verifiability | Contribs. check for Bio2RDF::Gendr took 2.048682451248169s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.38380861282348633s
Interlinking | skos check for Bio2RDF::Gendr took 0.9011015892028809s
Interlinking | skos check for Bio2RDF::Gendr took 0.3617136478424072s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.25257015228271484s
Currency | Creation date check for Bio2RDF::Gendr took 0.5058791637420654s
Currency | Modification date check for Bio2RDF::Gendr took 0.5015208721160889s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 109.98925471305847s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 12.82942008972168s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.44043421745300293s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.2761118412017822s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2828183174133301s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.062654972076416s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.906390905380249s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.676055908203125s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.441878080368042s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 66.14935612678528s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.485492467880249s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.640395879745483s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.3584296703338623s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.61710596084595s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7267615795135498s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.44245386123657227s
Security | Sign check for Bio2RDF::Gendr took 0.2816162109375s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 10.211950063705444s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.48700475692749023s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.02132248878479004s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007977485656738281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 6.246566772460938e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 13.00358247756958s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-gendr took 1201.7900404930115s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.4644796848297119s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0006864070892333984s
Extra | Recovery of all triples for Bio2RDF::Goa took 19.14799666404724s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.3944480419158936s
Amount of data | Number of triples check for Bio2RDF::Goa took 45.46845364570618s
Interoperability | New terms check for Bio2RDF::Goa took 42.9058883190155s
Versatility | Languages check for Bio2RDF::Goa took 60.250186920166016s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.2512531280517578s
Security | Check HTTPS for Bio2RDF::Goa took 0.17020416259765625s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.7143542766571045s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.31817126274108887s
Availability | RDF dump link check for Bio2RDF::Goa took 2.406663417816162s
License | MR license check for Bio2RDF::Goa took 0.37936997413635254s
License | HR license check for Bio2RDF::Goa took 60.256901264190674s
Amount of data | Number of property check for Bio2RDF::Goa took 0.2765772342681885s
Understandability | Number of label check for Bio2RDF::Goa took 9.652588367462158s
Understandability | URI regex check for Bio2RDF::Goa took 0.8635189533233643s
Understandability | Vocabs check for Bio2RDF::Goa took 0.252194881439209s
Verifiability | Authors check for Bio2RDF::Goa took 0.26363253593444824s
Verifiability | Publishers check for Bio2RDF::Goa took 0.2552330493927002s
Performance | Throughput check for Bio2RDF::Goa took 11.338660478591919s
Amount of data | Check the number of entities for Bio2RDF::Goa took 80.27366185188293s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.2624092102050781s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.3599517345428467s
Interlinking | skos check for Bio2RDF::Goa took 0.801276445388794s
Interlinking | skos check for Bio2RDF::Goa took 0.3476850986480713s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.26114583015441895s
Currency | Creation date check for Bio2RDF::Goa took 0.518836498260498s
Currency | Modification date check for Bio2RDF::Goa took 0.5278592109680176s
Rep.Conc. | URIs length for Bio2RDF::Goa took 109.179771900177s
Interoperability | New vocabularies check for Bio2RDF::Goa took 11.013631582260132s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.4567148685455322s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.3014554977416992s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.27851176261901855s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.198006629943848s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8979098796844482s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6618890762329102s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.40738582611083984s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.34030938148499s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.623610496520996s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.622175455093384s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3807499408721924s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.646425008773804s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7132358551025391s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.45697951316833496s
Security | Sign check for Bio2RDF::Goa took 0.2953531742095947s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 10.643081665039062s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.5792150497436523s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.021271705627441406s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 7.581710815429688e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 11.96883511543274s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-goa took 1185.256997346878s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.47871994972229004s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0007364749908447266s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 18.981263637542725s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2940900325775146s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 45.48840618133545s
Interoperability | New terms check for Bio2RDF::Hgnc took 43.65273118019104s
Versatility | Languages check for Bio2RDF::Hgnc took 60.26630902290344s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.3237488269805908s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.16149592399597168s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.7635667324066162s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.3377256393432617s
Availability | RDF dump link check for Bio2RDF::Hgnc took 2.352623462677002s
License | MR license check for Bio2RDF::Hgnc took 0.5573201179504395s
License | HR license check for Bio2RDF::Hgnc took 60.26234149932861s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.2818326950073242s
Understandability | Number of label check for Bio2RDF::Hgnc took 10.767904996871948s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5756731033325195s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.26933765411376953s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.27072954177856445s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.2605776786804199s
Performance | Throughput check for Bio2RDF::Hgnc took 10.346070766448975s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 83.41418814659119s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.6165895462036133s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.3504753112792969s
Interlinking | skos check for Bio2RDF::Hgnc took 0.704864501953125s
Interlinking | skos check for Bio2RDF::Hgnc took 0.38503384590148926s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2719902992248535s
Currency | Creation date check for Bio2RDF::Hgnc took 0.527820348739624s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5404491424560547s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 109.86471247673035s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 12.511366367340088s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.425518274307251s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.29682350158691406s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.2880675792694092s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 8.558775186538696s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.904888391494751s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6882321834564209s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.4198429584503174s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 66.060311794281s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.50946307182312s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.409896373748779s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.384810209274292s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.63481068611145s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7408015727996826s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.42275214195251465s
Security | Sign check for Bio2RDF::Hgnc took 0.2695648670196533s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 10.19202709197998s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 30.001911401748657s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020889759063720703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00012087821960449219s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 12.154726266860962s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1216.581193447113s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.46012425422668457s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0007269382476806641s
Extra | Recovery of all triples for Bio2RDF::Homologene took 18.803337812423706s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.238562822341919s
Amount of data | Number of triples check for Bio2RDF::Homologene took 45.57735204696655s
Interoperability | New terms check for Bio2RDF::Homologene took 41.73414373397827s
Versatility | Languages check for Bio2RDF::Homologene took 60.240071296691895s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.26575422286987305s
Security | Check HTTPS for Bio2RDF::Homologene took 0.1590888500213623s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.5896346569061279s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.31685471534729004s
Availability | RDF dump link check for Bio2RDF::Homologene took 2.146219253540039s
License | MR license check for Bio2RDF::Homologene took 0.47207045555114746s
License | HR license check for Bio2RDF::Homologene took 60.26227021217346s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.26849365234375s
Understandability | Number of label check for Bio2RDF::Homologene took 10.483039379119873s
Understandability | URI regex check for Bio2RDF::Homologene took 0.57747483253479s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.2540915012359619s
Verifiability | Authors check for Bio2RDF::Homologene took 0.2622721195220947s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.250838041305542s
Performance | Throughput check for Bio2RDF::Homologene took 10.404757976531982s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 84.1982433795929s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.5443019866943359s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.36177659034729004s
Interlinking | skos check for Bio2RDF::Homologene took 0.8604645729064941s
Interlinking | skos check for Bio2RDF::Homologene took 0.3594372272491455s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.28406333923339844s
Currency | Creation date check for Bio2RDF::Homologene took 0.5067732334136963s
Currency | Modification date check for Bio2RDF::Homologene took 0.5116426944732666s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 112.42681527137756s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 11.6135733127594s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.4481801986694336s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.27698707580566406s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.27533507347106934s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 7.303081035614014s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8941988945007324s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6788952350616455s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.396148681640625s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.16677117347717s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.7896170616149902s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.488325834274292s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3742780685424805s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.62687063217163s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7278177738189697s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.4651029109954834s
Security | Sign check for Bio2RDF::Homologene took 0.3040478229522705s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 9.592494010925293s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 27.038262605667114s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020952939987182617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 6.270408630371094e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 13.51698112487793s
Believability | Calculation of trust value for Bio2RDF::Homologene took 2.0265579223632812e-05s
INFO | --- Analysis for bio2rdf-homologene took 1165.9630842208862s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.54239821434021s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0006518363952636719s
Extra | Recovery of all triples for Bio2RDF::Interpro took 18.72829508781433s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2047393321990967s
Amount of data | Number of triples check for Bio2RDF::Interpro took 46.22137904167175s
Interoperability | New terms check for Bio2RDF::Interpro took 41.79543900489807s
Versatility | Languages check for Bio2RDF::Interpro took 60.248347759246826s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.2869100570678711s
Security | Check HTTPS for Bio2RDF::Interpro took 0.15622758865356445s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.8626353740692139s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.3326423168182373s
Availability | RDF dump link check for Bio2RDF::Interpro took 2.3082163333892822s
License | MR license check for Bio2RDF::Interpro took 0.5310742855072021s
License | HR license check for Bio2RDF::Interpro took 60.23441028594971s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.3101959228515625s
Understandability | Number of label check for Bio2RDF::Interpro took 10.027543306350708s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5824801921844482s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.24683094024658203s
Verifiability | Authors check for Bio2RDF::Interpro took 0.2571687698364258s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.24985313415527344s
Performance | Throughput check for Bio2RDF::Interpro took 10.974366903305054s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 85.00388145446777s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.2690424919128418s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.35578203201293945s
Interlinking | skos check for Bio2RDF::Interpro took 1.0698761940002441s
Interlinking | skos check for Bio2RDF::Interpro took 0.33257484436035156s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.24891877174377441s
Currency | Creation date check for Bio2RDF::Interpro took 0.5260589122772217s
Currency | Modification date check for Bio2RDF::Interpro took 0.5126023292541504s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 110.0061366558075s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 13.074657917022705s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.40297842025756836s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.2937357425689697s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2704737186431885s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 7.2516562938690186s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.9027402400970459s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6990227699279785s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.4662349224090576s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.32030820846558s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.723024368286133s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.363581418991089s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.3682472705841064s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.62330198287964s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7507851123809814s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.43206000328063965s
Security | Sign check for Bio2RDF::Interpro took 0.26618385314941406s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 10.045889616012573s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.4214773178100586s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.0211026668548584s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00016450881958007812s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 11.868566274642944s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-interpro took 1177.552493572235s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.1418600082397461s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 26.132434844970703s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.02110123634338379s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 9.083747863769531e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-iproclass took 166.77330994606018s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.6980063915252686s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0006992816925048828s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 18.604727506637573s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2647666931152344s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 45.783549308776855s
Interoperability | New terms check for Bio2RDF::Irefindex took 43.18176460266113s
Versatility | Languages check for Bio2RDF::Irefindex took 60.269378900527954s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.26819300651550293s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.17283415794372559s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.8657047748565674s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.32175207138061523s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.300820827484131s
License | MR license check for Bio2RDF::Irefindex took 0.49087095260620117s
License | HR license check for Bio2RDF::Irefindex took 60.23938822746277s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.26042771339416504s
Understandability | Number of label check for Bio2RDF::Irefindex took 10.448325157165527s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.5877285003662109s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.24846744537353516s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.2801644802093506s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.254716157913208s
Performance | Throughput check for Bio2RDF::Irefindex took 11.256743907928467s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 83.27553057670593s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.6053531169891357s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.3724510669708252s
Interlinking | skos check for Bio2RDF::Irefindex took 1.1693785190582275s
Interlinking | skos check for Bio2RDF::Irefindex took 0.33376383781433105s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.2741892337799072s
Currency | Creation date check for Bio2RDF::Irefindex took 0.4934196472167969s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5033504962921143s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 109.515056848526s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 12.538528442382812s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.44439125061035156s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2565946578979492s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.27193689346313477s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 6.710888147354126s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8968532085418701s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6782166957855225s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.4123349189758301s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 64.93227434158325s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.481443166732788s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.483669996261597s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.368154525756836s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.617167472839355s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7327542304992676s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.4787604808807373s
Security | Sign check for Bio2RDF::Irefindex took 0.28099751472473145s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 9.593443393707275s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 24.67507243156433s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.02102375030517578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 9.202957153320312e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 13.557528972625732s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1293.356482744217s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.13556981086730957s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 23.97121834754944s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.933906555175781e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 224.6022183895111s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.5640504360198975s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0006444454193115234s
Extra | Recovery of all triples for Bio2RDF::Lsr took 19.80087375640869s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2204713821411133s
Amount of data | Number of triples check for Bio2RDF::Lsr took 45.218501567840576s
Interoperability | New terms check for Bio2RDF::Lsr took 44.28938889503479s
Versatility | Languages check for Bio2RDF::Lsr took 60.24851655960083s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.2848019599914551s
Security | Check HTTPS for Bio2RDF::Lsr took 0.1457960605621338s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.750206708908081s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.34766149520874023s
Availability | RDF dump link check for Bio2RDF::Lsr took 2.2740092277526855s
License | MR license check for Bio2RDF::Lsr took 0.4563028812408447s
License | HR license check for Bio2RDF::Lsr took 60.250253200531006s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.30384349822998047s
Understandability | Number of label check for Bio2RDF::Lsr took 10.05724811553955s
Understandability | URI regex check for Bio2RDF::Lsr took 0.604337215423584s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.25169897079467773s
Verifiability | Authors check for Bio2RDF::Lsr took 0.25927257537841797s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.2611572742462158s
Performance | Throughput check for Bio2RDF::Lsr took 11.50639796257019s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 84.1617636680603s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.2786283493041992s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3551747798919678s
Interlinking | skos check for Bio2RDF::Lsr took 0.7577493190765381s
Interlinking | skos check for Bio2RDF::Lsr took 0.33961009979248047s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.2604670524597168s
Currency | Creation date check for Bio2RDF::Lsr took 0.5154097080230713s
Currency | Modification date check for Bio2RDF::Lsr took 0.532038688659668s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 112.21824526786804s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 14.55141282081604s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.42897796630859375s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.2598276138305664s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.2850804328918457s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 6.711264371871948s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.902127742767334s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6941978931427002s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.42275571823120117s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.02207899093628s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.6402339935302734s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.762244701385498s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.358067274093628s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.60134696960449s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7352511882781982s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.431502103805542s
Security | Sign check for Bio2RDF::Lsr took 0.2731621265411377s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 10.322432518005371s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 27.126912117004395s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.021218538284301758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 12.457371473312378s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-lsr took 1253.0526113510132s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.4846320152282715s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0007078647613525391s
Extra | Recovery of all triples for Bio2RDF::Mesh took 20.57405424118042s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2219102382659912s
Amount of data | Number of triples check for Bio2RDF::Mesh took 45.83555006980896s
Interoperability | New terms check for Bio2RDF::Mesh took 42.853238344192505s
Versatility | Languages check for Bio2RDF::Mesh took 60.24382925033569s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.2802004814147949s
Security | Check HTTPS for Bio2RDF::Mesh took 0.1566476821899414s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.984450101852417s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.31139445304870605s
Availability | RDF dump link check for Bio2RDF::Mesh took 2.3324084281921387s
License | MR license check for Bio2RDF::Mesh took 0.4854896068572998s
License | HR license check for Bio2RDF::Mesh took 60.24139928817749s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.2696366310119629s
Understandability | Number of label check for Bio2RDF::Mesh took 10.270370721817017s
Understandability | URI regex check for Bio2RDF::Mesh took 0.546886682510376s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.26431989669799805s
Verifiability | Authors check for Bio2RDF::Mesh took 0.24433493614196777s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.26252174377441406s
Performance | Throughput check for Bio2RDF::Mesh took 11.690042495727539s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 82.07796311378479s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.26895594596862793s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.33772778511047363s
Interlinking | skos check for Bio2RDF::Mesh took 0.758145809173584s
Interlinking | skos check for Bio2RDF::Mesh took 0.3446347713470459s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.27533650398254395s
Currency | Creation date check for Bio2RDF::Mesh took 0.5216450691223145s
Currency | Modification date check for Bio2RDF::Mesh took 0.5382394790649414s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 109.29547381401062s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 13.025733470916748s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.44054412841796875s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.282909631729126s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.27266716957092285s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 6.8380126953125s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.899174690246582s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6766557693481445s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.2921719551086426s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 66.16507530212402s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.8425424098968506s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.745177507400513s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3821938037872314s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.629026651382446s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.7118887901306152s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.448347806930542s
Security | Sign check for Bio2RDF::Mesh took 0.2652101516723633s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 10.786362648010254s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 25.16556739807129s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.0211181640625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.915496826171875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 13.870692253112793s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-mesh took 1197.0310389995575s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.47458338737487793s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0006465911865234375s
Extra | Recovery of all triples for Bio2RDF::Mgi took 19.695507764816284s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.296844720840454s
Amount of data | Number of triples check for Bio2RDF::Mgi took 45.3484890460968s
Interoperability | New terms check for Bio2RDF::Mgi took 41.1501247882843s
Versatility | Languages check for Bio2RDF::Mgi took 60.26878547668457s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.26090240478515625s
Security | Check HTTPS for Bio2RDF::Mgi took 0.17157435417175293s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.9655256271362305s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.3349118232727051s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.1998584270477295s
License | MR license check for Bio2RDF::Mgi took 0.4994058609008789s
License | HR license check for Bio2RDF::Mgi took 60.241697549819946s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.2712080478668213s
Understandability | Number of label check for Bio2RDF::Mgi took 9.480136394500732s
Understandability | URI regex check for Bio2RDF::Mgi took 0.6158304214477539s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.25878477096557617s
Verifiability | Authors check for Bio2RDF::Mgi took 0.2612574100494385s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.26048827171325684s
Performance | Throughput check for Bio2RDF::Mgi took 11.505745649337769s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 85.1113793849945s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.5993332862854004s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.36405301094055176s
Interlinking | skos check for Bio2RDF::Mgi took 1.0082612037658691s
Interlinking | skos check for Bio2RDF::Mgi took 0.36116719245910645s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.27478766441345215s
Currency | Creation date check for Bio2RDF::Mgi took 0.5075061321258545s
Currency | Modification date check for Bio2RDF::Mgi took 0.5290148258209229s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 112.43051314353943s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 13.794020414352417s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.42717623710632324s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.27079153060913086s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.2834930419921875s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.349475145339966s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.9000415802001953s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6882028579711914s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.46675896644592285s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.36779570579529s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.5053939819335938s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.90807843208313s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3805534839630127s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.624316692352295s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7349703311920166s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.48615550994873047s
Security | Sign check for Bio2RDF::Mgi took 0.27974724769592285s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 19.514251470565796s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 29.845627546310425s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.020971298217773438s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 0.00010132789611816406s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 11.266199111938477s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.6450881958007812e-05s
INFO | --- Analysis for bio2rdf-mgi took 1265.6058568954468s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.4884641170501709s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0006518363952636719s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 18.864495277404785s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2422780990600586s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 46.104300022125244s
Interoperability | New terms check for Bio2RDF::Ncbigene took 41.494420766830444s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.24560356140137s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.27001142501831055s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.15658044815063477s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.693120002746582s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.3123600482940674s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 2.3417742252349854s
License | MR license check for Bio2RDF::Ncbigene took 0.4932866096496582s
License | HR license check for Bio2RDF::Ncbigene took 60.26401996612549s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.29996490478515625s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.836950302124023s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.596341609954834s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.26752400398254395s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.2689039707183838s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.26314234733581543s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.044327735900879s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 83.86267256736755s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.7310726642608643s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.39806580543518066s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.7832105159759521s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.356478214263916s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.24851679801940918s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5157272815704346s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5153756141662598s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 109.6270534992218s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 12.809198141098022s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.4329044818878174s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.28944969177246094s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.28477907180786133s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 6.874713659286499s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8952903747558594s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6915087699890137s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.4501190185546875s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.39142894744873s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.462623119354248s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.350507974624634s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.3806381225585938s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.63964033126831s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7321228981018066s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.4498157501220703s
Security | Sign check for Bio2RDF::Ncbigene took 0.2948336601257324s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 9.887991666793823s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 25.046269178390503s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.021538257598876953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012755393981933594s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 13.990794897079468s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 1250.0942969322205s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.47896337509155273s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0006604194641113281s
Extra | Recovery of all triples for Bio2RDF::Ndc took 18.97841238975525s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2398545742034912s
Amount of data | Number of triples check for Bio2RDF::Ndc took 45.63326072692871s
Interoperability | New terms check for Bio2RDF::Ndc took 42.65382170677185s
Versatility | Languages check for Bio2RDF::Ndc took 60.23390865325928s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.28835272789001465s
Security | Check HTTPS for Bio2RDF::Ndc took 0.1696174144744873s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.824639081954956s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.34301090240478516s
Availability | RDF dump link check for Bio2RDF::Ndc took 2.275226593017578s
License | MR license check for Bio2RDF::Ndc took 0.6114776134490967s
License | HR license check for Bio2RDF::Ndc took 60.259713649749756s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.2848179340362549s
Understandability | Number of label check for Bio2RDF::Ndc took 10.044713497161865s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5926871299743652s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.26398658752441406s
Verifiability | Authors check for Bio2RDF::Ndc took 0.2657947540283203s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.2542288303375244s
Performance | Throughput check for Bio2RDF::Ndc took 11.04744839668274s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 85.84483242034912s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.5772683620452881s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.38362717628479004s
Interlinking | skos check for Bio2RDF::Ndc took 0.8598320484161377s
Interlinking | skos check for Bio2RDF::Ndc took 0.3381633758544922s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.2547159194946289s
Currency | Creation date check for Bio2RDF::Ndc took 0.48161792755126953s
Currency | Modification date check for Bio2RDF::Ndc took 0.5045325756072998s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 109.22365665435791s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 13.871787071228027s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.4507269859313965s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.26020312309265137s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.27086806297302246s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 7.5641443729400635s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.9005413055419922s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6872413158416748s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.37079882621765137s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.50218987464905s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.51243257522583s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.433836936950684s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.3642950057983398s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.62111783027649s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7457177639007568s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.45117712020874023s
Security | Sign check for Bio2RDF::Ndc took 0.2708749771118164s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 11.368719100952148s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 25.271552562713623s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.021047592163085938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 6.29425048828125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 13.309119462966919s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-ndc took 1215.6022334098816s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.13414597511291504s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.31204867362976074s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.021144628524780273s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.457069396972656e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-nextprot took 200.61573672294617s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.6689834594726562s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0007345676422119141s
Extra | Recovery of all triples for Bio2RDF::Omim took 18.91116166114807s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.2426366806030273s
Amount of data | Number of triples check for Bio2RDF::Omim took 45.23630690574646s
Interoperability | New terms check for Bio2RDF::Omim took 42.59562015533447s
Versatility | Languages check for Bio2RDF::Omim took 60.25115418434143s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.29921770095825195s
Security | Check HTTPS for Bio2RDF::Omim took 0.16949772834777832s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.9663043022155762s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.3883657455444336s
Availability | RDF dump link check for Bio2RDF::Omim took 2.370389938354492s
License | MR license check for Bio2RDF::Omim took 0.5227136611938477s
License | HR license check for Bio2RDF::Omim took 60.23624324798584s
Amount of data | Number of property check for Bio2RDF::Omim took 0.288970947265625s
Understandability | Number of label check for Bio2RDF::Omim took 10.6085684299469s
Understandability | URI regex check for Bio2RDF::Omim took 0.6004581451416016s
Understandability | Vocabs check for Bio2RDF::Omim took 0.25958681106567383s
Verifiability | Authors check for Bio2RDF::Omim took 0.2508552074432373s
Verifiability | Publishers check for Bio2RDF::Omim took 0.26050662994384766s
Performance | Throughput check for Bio2RDF::Omim took 10.99838900566101s
Amount of data | Check the number of entities for Bio2RDF::Omim took 82.67438101768494s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.5959181785583496s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.41504907608032227s
Interlinking | skos check for Bio2RDF::Omim took 0.7286772727966309s
Interlinking | skos check for Bio2RDF::Omim took 0.3362410068511963s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.2576632499694824s
Currency | Creation date check for Bio2RDF::Omim took 0.5247249603271484s
Currency | Modification date check for Bio2RDF::Omim took 0.4882209300994873s
Rep.Conc. | URIs length for Bio2RDF::Omim took 109.72142171859741s
Interoperability | New vocabularies check for Bio2RDF::Omim took 13.741653680801392s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4280731678009033s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.27364373207092285s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.30577754974365234s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 7.2994349002838135s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8948655128479004s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6858234405517578s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.415299654006958s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.0871787071228s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.4947471618652344s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.476227045059204s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.3665456771850586s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.61448931694031s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7301414012908936s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.4675266742706299s
Security | Sign check for Bio2RDF::Omim took 0.31392717361450195s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 9.38027024269104s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 28.25169563293457s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.021307945251464844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0009734630584716797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00015783309936523438s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 12.235707998275757s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-omim took 1183.7880713939667s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.696846008300781e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 24.07705521583557s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.0221710205078125s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.553794860839844e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 191.03822541236877s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 2.110856294631958s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0007386207580566406s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 18.381913900375366s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2801518440246582s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 47.53335881233215s
Interoperability | New terms check for Bio2RDF::Orphanet took 41.67881512641907s
Versatility | Languages check for Bio2RDF::Orphanet took 60.49243640899658s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.293956995010376s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.15774846076965332s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.7688639163970947s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.31664133071899414s
Availability | RDF dump link check for Bio2RDF::Orphanet took 2.3517777919769287s
License | MR license check for Bio2RDF::Orphanet took 0.47531890869140625s
License | HR license check for Bio2RDF::Orphanet took 60.24379515647888s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.2609279155731201s
Understandability | Number of label check for Bio2RDF::Orphanet took 9.99920129776001s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.6011207103729248s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.24329566955566406s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.2571723461151123s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.25939178466796875s
Performance | Throughput check for Bio2RDF::Orphanet took 10.827415227890015s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 84.54626226425171s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.24306774139404297s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.3372316360473633s
Interlinking | skos check for Bio2RDF::Orphanet took 0.7925221920013428s
Interlinking | skos check for Bio2RDF::Orphanet took 0.35813236236572266s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.24983859062194824s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5182211399078369s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5166528224945068s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 109.99659872055054s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 12.068751573562622s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.44332456588745117s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2613499164581299s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2779359817504883s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 7.215915203094482s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.9145190715789795s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.686159610748291s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.38625216484069824s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.03860521316528s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.742107391357422s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.7820329666137695s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.368448257446289s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.58580207824707s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7293179035186768s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.454425573348999s
Security | Sign check for Bio2RDF::Orphanet took 0.27340006828308105s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 10.068256616592407s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.5160539150238037s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02244091033935547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.416175842285156e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 12.664064884185791s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 2.0503997802734375e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1185.640605688095s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.1423172950744629s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 27.664211988449097s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.027300596237182617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.8623809814453125e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-pathwaycommons took 95.39795160293579s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.5413942337036133s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.00040650367736816406s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 18.814194917678833s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2435364723205566s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 47.200785398483276s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 42.09899973869324s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.23568868637085s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.2960634231567383s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.16832232475280762s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.5315470695495605s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.34372997283935547s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 2.2432899475097656s
License | MR license check for Bio2RDF::Pharmgkb took 0.5394577980041504s
License | HR license check for Bio2RDF::Pharmgkb took 60.256540060043335s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.25596141815185547s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 9.954692840576172s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5757765769958496s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.26531291007995605s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.27202534675598145s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.2510488033294678s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.309417009353638s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 84.73718547821045s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.2508049011230469s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.36250758171081543s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.9668850898742676s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.35373473167419434s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.25655698776245117s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5119118690490723s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5089406967163086s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 111.33776116371155s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 14.346682071685791s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.45366787910461426s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.27268052101135254s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.2789628505706787s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 7.470498323440552s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8958191871643066s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.707669734954834s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.3652069568634033s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 64.96601366996765s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.7201168537139893s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.267406225204468s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.3734025955200195s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.596572399139404s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7374722957611084s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.475879430770874s
Security | Sign check for Bio2RDF::Pharmgkb took 0.2789790630340576s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 11.224016904830933s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.5719974040985107s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.021091938018798828s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.557868957519531e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 12.764395952224731s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 1199.3083775043488s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.5030574798583984s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0007603168487548828s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 19.6957790851593s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2303338050842285s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 47.53321194648743s
Interoperability | New terms check for Bio2RDF::Pubmed took 45.11302065849304s
Versatility | Languages check for Bio2RDF::Pubmed took 60.255722999572754s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.2714087963104248s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.1476898193359375s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.7679750919342041s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.3482654094696045s
Availability | RDF dump link check for Bio2RDF::Pubmed took 2.058197498321533s
License | MR license check for Bio2RDF::Pubmed took 0.493267297744751s
License | HR license check for Bio2RDF::Pubmed took 60.25121879577637s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.28295040130615234s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.602881908416748s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5877907276153564s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.2579779624938965s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.24861931800842285s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.24759387969970703s
Performance | Throughput check for Bio2RDF::Pubmed took 12.311396360397339s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 80.21990656852722s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.24614596366882324s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.3432440757751465s
Interlinking | skos check for Bio2RDF::Pubmed took 0.9935762882232666s
Interlinking | skos check for Bio2RDF::Pubmed took 0.34603118896484375s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2516026496887207s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5184657573699951s
Currency | Modification date check for Bio2RDF::Pubmed took 0.52571702003479s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 109.02816987037659s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 13.116829872131348s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.4597759246826172s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.28876352310180664s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.267749547958374s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 6.9169206619262695s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8994631767272949s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6691703796386719s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.4648604393005371s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.4150562286377s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.5800864696502686s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.468380689620972s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.374215841293335s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.611518144607544s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.724937915802002s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.4370598793029785s
Security | Sign check for Bio2RDF::Pubmed took 0.2876265048980713s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 10.225449800491333s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.3511388301849365s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.02091383934020996s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.0001392364501953125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 11.588530778884888s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 2.3126602172851562e-05s
INFO | --- Analysis for bio2rdf-pubmed took 1248.2271835803986s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.1431722640991211s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 28.147679328918457s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.02221393585205078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 8.869171142578125e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-sabiork took 200.39004826545715s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.6835088729858398s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0006191730499267578s
Extra | Recovery of all triples for Bio2RDF::Sgd took 18.99479055404663s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2281947135925293s
Amount of data | Number of triples check for Bio2RDF::Sgd took 46.35213589668274s
Interoperability | New terms check for Bio2RDF::Sgd took 42.829708099365234s
Versatility | Languages check for Bio2RDF::Sgd took 60.2407603263855s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.27921223640441895s
Security | Check HTTPS for Bio2RDF::Sgd took 0.1452159881591797s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.7086725234985352s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.31717348098754883s
Availability | RDF dump link check for Bio2RDF::Sgd took 2.43184494972229s
License | MR license check for Bio2RDF::Sgd took 0.5207736492156982s
License | HR license check for Bio2RDF::Sgd took 60.250072717666626s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.2872939109802246s
Understandability | Number of label check for Bio2RDF::Sgd took 10.033925771713257s
Understandability | URI regex check for Bio2RDF::Sgd took 0.5632402896881104s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.23315906524658203s
Verifiability | Authors check for Bio2RDF::Sgd took 0.2639937400817871s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.25535154342651367s
Performance | Throughput check for Bio2RDF::Sgd took 11.221422672271729s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 84.46251320838928s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.5773091316223145s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.35062313079833984s
Interlinking | skos check for Bio2RDF::Sgd took 0.764955997467041s
Interlinking | skos check for Bio2RDF::Sgd took 0.3631415367126465s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2727823257446289s
Currency | Creation date check for Bio2RDF::Sgd took 0.5257747173309326s
Currency | Modification date check for Bio2RDF::Sgd took 0.5199308395385742s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 109.0007050037384s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 12.17416763305664s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.4514775276184082s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2880370616912842s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.29244303703308105s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.827371835708618s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.898418664932251s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6717689037322998s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.4692695140838623s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 64.89753317832947s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.511251926422119s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.317880868911743s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3616266250610352s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.616026639938354s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7266445159912109s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.45879507064819336s
Security | Sign check for Bio2RDF::Sgd took 0.2870340347290039s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 9.983439207077026s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.5690932273864746s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.021392107009887695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00013136863708496094s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 12.788625955581665s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-sgd took 1164.7972583770752s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.4345855712890625e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 30.700839281082153s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020877599716186523s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 4.6253204345703125e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 220.7941472530365s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.6494243144989014s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0006601810455322266s
Extra | Recovery of all triples for Bio2RDF::Sider took 19.479193449020386s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2455718517303467s
Amount of data | Number of triples check for Bio2RDF::Sider took 47.416975021362305s
Interoperability | New terms check for Bio2RDF::Sider took 43.306893825531006s
Versatility | Languages check for Bio2RDF::Sider took 60.257195472717285s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.294086217880249s
Security | Check HTTPS for Bio2RDF::Sider took 0.15466880798339844s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.915658712387085s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.3676433563232422s
Availability | RDF dump link check for Bio2RDF::Sider took 2.214587450027466s
License | MR license check for Bio2RDF::Sider took 0.631810188293457s
License | HR license check for Bio2RDF::Sider took 60.25643515586853s
Amount of data | Number of property check for Bio2RDF::Sider took 0.28239965438842773s
Understandability | Number of label check for Bio2RDF::Sider took 9.85872507095337s
Understandability | URI regex check for Bio2RDF::Sider took 0.5851235389709473s
Understandability | Vocabs check for Bio2RDF::Sider took 0.27603769302368164s
Verifiability | Authors check for Bio2RDF::Sider took 0.28562188148498535s
Verifiability | Publishers check for Bio2RDF::Sider took 0.2733500003814697s
Performance | Throughput check for Bio2RDF::Sider took 10.835399389266968s
Amount of data | Check the number of entities for Bio2RDF::Sider took 84.41157841682434s
Verifiability | Contribs. check for Bio2RDF::Sider took 2.0416128635406494s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.37090063095092773s
Interlinking | skos check for Bio2RDF::Sider took 0.8793172836303711s
Interlinking | skos check for Bio2RDF::Sider took 0.33801960945129395s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.2581174373626709s
Currency | Creation date check for Bio2RDF::Sider took 0.5285830497741699s
Currency | Modification date check for Bio2RDF::Sider took 0.5292131900787354s
Rep.Conc. | URIs length for Bio2RDF::Sider took 110.86991834640503s
Interoperability | New vocabularies check for Bio2RDF::Sider took 13.07218861579895s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.48349857330322266s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.2779388427734375s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2656443119049072s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 6.892397403717041s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8983376026153564s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6867036819458008s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.3909308910369873s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.0727527141571s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.452293634414673s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 7.192128896713257s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.3687725067138672s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.597083568573s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7164621353149414s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.47300195693969727s
Security | Sign check for Bio2RDF::Sider took 0.2677757740020752s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 11.076947927474976s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.5747213363647461s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020982742309570312s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 11.635596752166748s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-sider took 1176.9553437232971s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 0.00010180473327636719s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006928443908691406s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 24.17195749282837s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 5.340576171875e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-taxon took 186.78153705596924s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.6664962768554688s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0006759166717529297s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 19.982649087905884s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2152385711669922s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 46.074421882629395s
Interoperability | New terms check for Bio2RDF::Taxonomy took 42.889548540115356s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.25955414772034s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.27602148056030273s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.16079187393188477s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.29642486572265625s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.35420894622802734s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 2.4438998699188232s
License | MR license check for Bio2RDF::Taxonomy took 0.5460474491119385s
License | HR license check for Bio2RDF::Taxonomy took 60.2640860080719s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.2724800109863281s
Understandability | Number of label check for Bio2RDF::Taxonomy took 10.875211238861084s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5982599258422852s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.2551703453063965s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.27126193046569824s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.2595553398132324s
Performance | Throughput check for Bio2RDF::Taxonomy took 61.57558274269104s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 85.03005480766296s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.24300789833068848s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.3632056713104248s
Interlinking | skos check for Bio2RDF::Taxonomy took 1.0303730964660645s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.3607621192932129s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.27137017250061035s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5191400051116943s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.533099889755249s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 110.57127976417542s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 12.891561269760132s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 22.077557802200317s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.44488525390625s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.2717595100402832s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 6.906626224517822s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8963909149169922s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6912097930908203s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.402540922164917s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.54538345336914s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.4805002212524414s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.297369718551636s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.3808958530426025s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.64384579658508s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7261431217193604s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.4329488277435303s
Security | Sign check for Bio2RDF::Taxonomy took 0.26079273223876953s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 10.045598983764648s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.44899749755859375s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.021596670150756836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010776519775390625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 11.629979848861694s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 1302.527271747589s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.1385657787322998s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0007178783416748047s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 23.267006874084473s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.021585702896118164s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 4.506111145019531e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.9073486328125e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 153.50809979438782s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.47894954681396484s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0007174015045166016s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 19.346396684646606s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.2453970909118652s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 45.89034128189087s
Interoperability | New terms check for Bio2RDF::Wormbase took 41.213618755340576s
Versatility | Languages check for Bio2RDF::Wormbase took 60.24989414215088s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.3160974979400635s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.15894699096679688s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.7273099422454834s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.34967970848083496s
Availability | RDF dump link check for Bio2RDF::Wormbase took 2.36140513420105s
License | MR license check for Bio2RDF::Wormbase took 0.47835469245910645s
License | HR license check for Bio2RDF::Wormbase took 60.25747990608215s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.26337718963623047s
Understandability | Number of label check for Bio2RDF::Wormbase took 10.392555236816406s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.6063268184661865s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.2709157466888428s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.2800023555755615s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.2544114589691162s
Performance | Throughput check for Bio2RDF::Wormbase took 10.890626192092896s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 82.86895561218262s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.5780467987060547s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.3527364730834961s
Interlinking | skos check for Bio2RDF::Wormbase took 0.6949818134307861s
Interlinking | skos check for Bio2RDF::Wormbase took 0.34394288063049316s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.27576184272766113s
Currency | Creation date check for Bio2RDF::Wormbase took 0.4972496032714844s
Currency | Modification date check for Bio2RDF::Wormbase took 0.7778451442718506s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 108.67284083366394s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 11.02933931350708s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.48548197746276855s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.2804231643676758s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.285738468170166s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 6.928221225738525s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8959145545959473s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.680795431137085s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.4228091239929199s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.30563402175903s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.4693617820739746s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.5037806034088135s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.3804163932800293s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.62923192977905s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7279763221740723s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.4418809413909912s
Security | Sign check for Bio2RDF::Wormbase took 0.26633644104003906s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 9.902352571487427s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.6135308742523193s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.021033525466918945s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 9.608268737792969e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 11.753867864608765s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-wormbase took 1166.5640451908112s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.5424590110778809s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 25.70532536506653s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.022287845611572266s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 9.608268737792969e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 1.0251998901367188e-05s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 140.7870228290558s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 0.00010919570922851562s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 26.291837453842163s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020946979522705078s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 5.030632019042969e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 7.3909759521484375e-06s
INFO | --- Analysis for biolod-pdb took 193.2991964817047s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.699251651763916s
Availability | VoID file availability check for BioModels RDF took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for BioModels RDF took 25.11316704750061s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020992517471313477s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 4.553794860839844e-05s
Believability | Calculation of trust value for BioModels RDF took 1.3113021850585938e-05s
INFO | --- Analysis for biomodels-rdf took 169.2402858734131s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.8111329078674316s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007951259613037109s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 29.64103603363037s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02086782455444336s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.00543212890625e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.2636184692382812e-05s
INFO | --- Analysis for Biop took 172.04215669631958s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0001201629638671875s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0004074573516845703s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 25.84581756591797s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02087855339050293s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.839897155761719e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.58306884765625e-06s
INFO | --- Analysis for Bioportal took 184.7504596710205s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 9.393692016601562e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.31159543991088867s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.02090597152709961s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006372928619384766s
Believability | Calculation of trust value for Amphibian gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-aao took 155.59558939933777s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.76837158203125e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 22.473920583724976s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.020937204360961914s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0003142356872558594s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-aba took 74.07870554924011s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.28968286514282227s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.021592378616333008s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015382766723632812s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-acgt took 106.30501246452332s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 0.00010156631469726562s
Availability | VoID file availability check for Animal natural history and life history took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.3017537593841553s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003600120544433594s
Believability | Calculation of trust value for Animal natural history and life history took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-adw took 183.82466673851013s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 9.369850158691406e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 27.384164810180664s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.02095341682434082s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004775524139404297s
Believability | Calculation of trust value for Anatomical Entity Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-aeo took 101.73240733146667s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 9.298324584960938e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 25.251049757003784s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.021443605422973633s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0010235309600830078s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-aero took 189.83800649642944s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.506111145019531e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 32.157546043395996s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.021090269088745117s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.00042128562927246094s
Believability | Calculation of trust value for AI/RHEUM took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-air took 160.03447127342224s
Availability | SPARQL endpoint availability check for Amino Acid took 0.00010013580322265625s
Availability | VoID file availability check for Amino Acid took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for Amino Acid took 24.196632862091064s
Reputation | Calculation of the PageRank for Amino Acid took 0.021044254302978516s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002696514129638672s
Believability | Calculation of trust value for Amino Acid took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-amino-acid took 240.40503573417664s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 9.799003601074219e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.31102705001831055s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.021239042282104492s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.00034117698669433594s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-apo took 54.096277475357056s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.4345855712890625e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.29228901863098145s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.021432161331176758s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00025773048400878906s
Believability | Calculation of trust value for African Traditional Medicine took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-atmo took 185.38779258728027s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 0.00010347366333007812s
Availability | VoID file availability check for Amphibian taxonomy took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.29840707778930664s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.021403074264526367s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.1552734375e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ato took 94.89431500434875s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 9.799003601074219e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 28.691158294677734s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.0211641788482666s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013599395751953125s
Believability | Calculation of trust value for BioAssay Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bao took 158.94703125953674s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 9.417533874511719e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 35.456265926361084s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020931720733642578s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003991127014160156s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 264.60201501846313s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 9.393692016601562e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 23.316911935806274s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.02222132682800293s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0008094310760498047s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.00036835670471191406s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bcgo took 158.74468111991882s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 9.775161743164062e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.3367271423339844s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.021017074584960938s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.001407623291015625s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bdo took 138.4107346534729s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 9.250640869140625e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.39928555488586426s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.021342992782592773s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0008141994476318359s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005402565002441406s
Believability | Calculation of trust value for Basic Formal Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bfo took 98.70172691345215s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 0.00010609626770019531s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.31933045387268066s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.021166324615478516s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0008378028869628906s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007789134979248047s
Believability | Calculation of trust value for Bleeding History Phenotype took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bho took 143.02066779136658s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 9.799003601074219e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 26.743828535079956s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.02151799201965332s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 7.700920104980469e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.00046944618225097656s
Believability | Calculation of trust value for Bilateria anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bila took 106.54666757583618s
Availability | SPARQL endpoint availability check for BIRNLex took 7.033348083496094e-05s
Availability | VoID file availability check for BIRNLex took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for BIRNLex took 28.866190671920776s
Reputation | Calculation of the PageRank for BIRNLex took 0.0213778018951416s
Interlinking | Calculation of Degree of Connection for BIRNLex took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0015230178833007812s
Believability | Calculation of trust value for BIRNLex took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-birnlex took 195.98932814598083s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 9.131431579589844e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0003445148468017578s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 29.946895122528076s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.021198272705078125s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007865428924560547s
Believability | Calculation of trust value for Gene Regulation Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bootstrep took 153.86509442329407s
Availability | SPARQL endpoint availability check for BioPAX took 0.000152587890625s
Availability | VoID file availability check for BioPAX took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for BioPAX took 0.2939276695251465s
Reputation | Calculation of the PageRank for BioPAX took 0.02102184295654297s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.00011706352233886719s
Believability | Calculation of trust value for BioPAX took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bp took 51.93199348449707s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 23.424924612045288s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020972728729248047s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003757476806640625s
Believability | Calculation of trust value for Biomedical Resource Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bro_x1 took 173.6525363922119s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 24.033931493759155s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.021791934967041016s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.0002384185791015625s
Believability | Calculation of trust value for Spatial Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-bspo took 226.58646392822266s
Availability | SPARQL endpoint availability check for BioTop took 4.506111145019531e-05s
Availability | VoID file availability check for BioTop took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for BioTop took 0.3086240291595459s
Reputation | Calculation of the PageRank for BioTop took 0.021652698516845703s
Interlinking | Calculation of Degree of Connection for BioTop took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0007328987121582031s
Believability | Calculation of trust value for BioTop took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bt took 80.78015971183777s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 8.797645568847656e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.00039076805114746094s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 38.3719277381897s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.021753311157226562s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0011310577392578125s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.000997304916381836s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bto took 205.26128935813904s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 6.508827209472656e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3559746742248535s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.022436857223510742s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018815994262695312s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-canco took 121.08244323730469s
Availability | SPARQL endpoint availability check for CAO took 9.131431579589844e-05s
Availability | VoID file availability check for CAO took 0.0003712177276611328s
Completeness | Calculation of interlinking completeness for CAO took 28.399600982666016s
Reputation | Calculation of the PageRank for CAO took 0.020847558975219727s
Interlinking | Calculation of Degree of Connection for CAO took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for CAO took 0.000644683837890625s
Believability | Calculation of trust value for CAO took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-cao took 107.5902407169342s
Availability | SPARQL endpoint availability check for CareLex took 4.482269287109375e-05s
Availability | VoID file availability check for CareLex took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for CareLex took 24.26386857032776s
Reputation | Calculation of the PageRank for CareLex took 0.021238088607788086s
Interlinking | Calculation of Degree of Connection for CareLex took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0008416175842285156s
Interlinking | Calculation of Clustering coefficient for CareLex took 6.771087646484375e-05s
Believability | Calculation of trust value for CareLex took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-carelex took 230.6649444103241s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 6.508827209472656e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 34.20110607147217s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.02121591567993164s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0008325576782226562s
Believability | Calculation of trust value for Cell Cycle Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cco took 259.7393391132355s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 0.00015664100646972656s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 24.583134651184082s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.023270845413208008s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00026869773864746094s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-cdao took 172.0917775630951s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 9.417533874511719e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0003292560577392578s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.31656718254089355s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.021645545959472656s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0009272098541259766s
Believability | Calculation of trust value for Chemical entities of biological interest took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-chebi took 101.31309914588928s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 9.417533874511719e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.287020206451416s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.02239990234375s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002663135528564453s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 95.43649005889893s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 0.00016808509826660156s
Availability | VoID file availability check for Chemical Information Ontology took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.312502384185791s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.02110147476196289s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0008542537689208984s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0008714199066162109s
Believability | Calculation of trust value for Chemical Information Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cheminf took 157.92623472213745s
Availability | SPARQL endpoint availability check for Cell type took 9.584426879882812e-05s
Availability | VoID file availability check for Cell type took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Cell type took 0.2948877811431885s
Reputation | Calculation of the PageRank for Cell type took 0.021745920181274414s
Interlinking | Calculation of Degree of Connection for Cell type took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.00040650367736816406s
Believability | Calculation of trust value for Cell type took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-cl took 119.5208203792572s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 9.5367431640625e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.31179261207580566s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.021062612533569336s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 3.218650817871094e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008318424224853516s
Believability | Calculation of trust value for Cell Line Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-clo took 131.6825442314148s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 0.0001544952392578125s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.31148409843444824s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.02136397361755371s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00019979476928710938s
Believability | Calculation of trust value for Clinical Measurement Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-cmo took 110.7950644493103s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 0.00010633468627929688s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.00038933753967285156s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 35.1726861000061s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.022931814193725586s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00024056434631347656s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cno took 226.92266702651978s
Availability | SPARQL endpoint availability check for Wheat trait took 4.38690185546875e-05s
Availability | VoID file availability check for Wheat trait took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Wheat trait took 24.5505268573761s
Reputation | Calculation of the PageRank for Wheat trait took 0.02142333984375s
Interlinking | Calculation of Degree of Connection for Wheat trait took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.8650970458984375e-05s
Believability | Calculation of trust value for Wheat trait took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-co_wheat took 141.3795440196991s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 5.125999450683594e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 26.118412494659424s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.021150588989257812s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003693103790283203s
Believability | Calculation of trust value for Cognitive Atlas took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cogat took 147.8936448097229s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 9.298324584960938e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.3176405429840088s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020979642868041992s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0008838176727294922s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0008633136749267578s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-cogpo took 175.86898803710938s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 6.031990051269531e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 25.55142331123352s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.02279186248779297s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004382133483886719s
Believability | Calculation of trust value for Current Procedural Terminology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cpt took 157.64454007148743s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 0.0001010894775390625s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 33.748573541641235s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.022566795349121094s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017323493957519531s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-csp took 153.46574807167053s
Availability | SPARQL endpoint availability check for COSTART took 9.441375732421875e-05s
Availability | VoID file availability check for COSTART took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for COSTART took 0.31337404251098633s
Reputation | Calculation of the PageRank for COSTART took 0.02163553237915039s
Interlinking | Calculation of Degree of Connection for COSTART took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for COSTART took 0.00116729736328125s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0012621879577636719s
Believability | Calculation of trust value for COSTART took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-cst took 79.04358220100403s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.887580871582031e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 30.00935459136963s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.022873401641845703s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005345344543457031s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ctcae took 135.9852933883667s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 9.5367431640625e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 29.89717698097229s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.021300315856933594s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004858970642089844s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ctx took 131.56972742080688s
Availability | SPARQL endpoint availability check for Dendritic cell took 0.000118255615234375s
Availability | VoID file availability check for Dendritic cell took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Dendritic cell took 30.336601495742798s
Reputation | Calculation of the PageRank for Dendritic cell took 0.02095794677734375s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0003304481506347656s
Believability | Calculation of trust value for Dendritic cell took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-dc_cl took 159.94204688072205s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.76837158203125e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 24.40447211265564s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.020930767059326172s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 9.942054748535156e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ddanat took 158.69702172279358s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 5.221366882324219e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 26.707626581192017s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.02275848388671875s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009882450103759766s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ddi took 136.7844741344452s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.34465622901916504s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.02112436294555664s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 9.751319885253906e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-diagnosticont took 170.6069016456604s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 25.627392530441284s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.021355152130126953s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.000179290771484375s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 224.84725737571716s
Availability | SPARQL endpoint availability check for Human disease ontology took 6.699562072753906e-05s
Availability | VoID file availability check for Human disease ontology took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Human disease ontology took 29.15029549598694s
Reputation | Calculation of the PageRank for Human disease ontology took 0.021930932998657227s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0007607936859130859s
Believability | Calculation of trust value for Human disease ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-doid took 177.7352397441864s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 5.125999450683594e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 28.412940740585327s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.021060466766357422s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008406639099121094s
Believability | Calculation of trust value for Electrocardiography Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ecg took 197.04626321792603s
Availability | SPARQL endpoint availability check for Evidence codes took 0.00011467933654785156s
Availability | VoID file availability check for Evidence codes took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Evidence codes took 23.253249883651733s
Reputation | Calculation of the PageRank for Evidence codes took 0.021016359329223633s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 4.1484832763671875e-05s
Believability | Calculation of trust value for Evidence codes took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-eco took 226.09704732894897s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3927645683288574s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.021327972412109375s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017976760864257812s
Believability | Calculation of trust value for Experimental Factor Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-efo took 164.88165974617004s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 0.00010013580322265625s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 28.6260724067688s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.021015167236328125s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011773109436035156s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ehda took 165.28809928894043s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 0.0001857280731201172s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.2770991325378418s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.021894454956054688s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007274150848388672s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ehdaa took 105.34168410301208s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.553794860839844e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.31468844413757324s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.0224149227142334s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0006692409515380859s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 119.22583985328674s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 9.083747863769531e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 25.706950187683105s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.021016359329223633s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.075599670410156e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-emap took 163.91005110740662s
Availability | SPARQL endpoint availability check for Environment Ontology took 9.417533874511719e-05s
Availability | VoID file availability check for Environment Ontology took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.3548426628112793s
Reputation | Calculation of the PageRank for Environment Ontology took 0.022028684616088867s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0008206367492675781s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00045990943908691406s
Believability | Calculation of trust value for Environment Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-envo took 156.7686424255371s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 9.560585021972656e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 29.074405193328857s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020834922790527344s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0008108615875244141s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00032067298889160156s
Believability | Calculation of trust value for Plant environmental conditions took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-eo took 87.57377743721008s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 9.250640869140625e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 21.973217010498047s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.021043777465820312s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012581348419189453s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 1.6927719116210938e-05s
INFO | --- Analysis for bioportal-ep took 184.94829487800598s
Availability | SPARQL endpoint availability check for Epilepsy took 9.989738464355469e-05s
Availability | VoID file availability check for Epilepsy took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.30272984504699707s
Reputation | Calculation of the PageRank for Epilepsy took 0.021100759506225586s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00015974044799804688s
Believability | Calculation of trust value for Epilepsy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-epileponto took 87.34242820739746s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 9.322166442871094e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.3336477279663086s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020825624465942383s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.00119781494140625s
Believability | Calculation of trust value for eagle-i research resource ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ero took 75.6853678226471s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.6253204345703125e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 27.366729021072388s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.023087263107299805s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0011906623840332031s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0014047622680664062s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ev took 150.90160012245178s
Availability | SPARQL endpoint availability check for ExO took 9.012222290039062e-05s
Availability | VoID file availability check for ExO took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for ExO took 0.2992126941680908s
Reputation | Calculation of the PageRank for ExO took 0.021387815475463867s
Interlinking | Calculation of Degree of Connection for ExO took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00025916099548339844s
Believability | Calculation of trust value for ExO took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-exo took 154.1611967086792s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 9.417533874511719e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.00031948089599609375s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 25.34424138069153s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020966053009033203s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00013375282287597656s
Believability | Calculation of trust value for Fungal gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fao took 215.20051455497742s
Availability | SPARQL endpoint availability check for Biological imaging methods took 7.200241088867188e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.3364853858947754s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.023014545440673828s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 2.8133392333984375e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0012574195861816406s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.0003142356872558594s
Believability | Calculation of trust value for Biological imaging methods took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-fbbi took 77.5687427520752s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 5.125999450683594e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 24.87965416908264s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.021126985549926758s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006799697875976562s
Believability | Calculation of trust value for Drosophila gross anatomy took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-fbbt took 189.24336624145508s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 9.632110595703125e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.31123852729797363s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.021966934204101562s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 3.123283386230469e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0012094974517822266s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0006000995635986328s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fbcv took 89.76891422271729s
Availability | SPARQL endpoint availability check for Drosophila development took 5.412101745605469e-05s
Availability | VoID file availability check for Drosophila development took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for Drosophila development took 29.466965675354004s
Reputation | Calculation of the PageRank for Drosophila development took 0.02331256866455078s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 6.0558319091796875e-05s
Believability | Calculation of trust value for Drosophila development took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-fbdv took 222.8727834224701s
Availability | SPARQL endpoint availability check for Fly taxonomy took 5.0067901611328125e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0007634162902832031s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 26.773536682128906s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.0209043025970459s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003886222839355469s
Believability | Calculation of trust value for Fly taxonomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fbsp took 137.3398826122284s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 0.00015592575073242188s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 26.939985036849976s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.02096390724182129s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00023221969604492188s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 108.40770602226257s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 9.822845458984375e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 23.04168438911438s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.02102041244506836s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.00048828125s
Believability | Calculation of trust value for Family Health History Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-fhho took 195.06585478782654s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.3079710006713867s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.02219986915588379s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010750293731689453s
Believability | Calculation of trust value for Influenza Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-flu took 110.00207281112671s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.839897155761719e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 30.980154752731323s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.021005868911743164s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 8.797645568847656e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-fma took 158.84520554542542s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 9.131431579589844e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 23.403223991394043s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.02091193199157715s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00013327598571777344s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fypo took 173.60043287277222s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 9.274482727050781e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 29.344616889953613s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.021203041076660156s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 0.00010061264038085938s
Believability | Calculation of trust value for GeoSpecies Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-geospecies took 212.06017589569092s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 24.428653240203857s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.021187305450439453s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.0001766681671142578s
Believability | Calculation of trust value for General Formal Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-gfo took 128.42006540298462s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 9.441375732421875e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.3166375160217285s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.02138972282409668s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006201267242431641s
Believability | Calculation of trust value for General Formal Ontology: Biology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-gfo-bio took 111.41516923904419s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 9.202957153320312e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 29.6155264377594s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.021332502365112305s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008935928344726562s
Believability | Calculation of trust value for Gene Ontology Extension took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-go_x1 took 118.90789127349854s
Availability | SPARQL endpoint availability check for Gene Ontology took 9.489059448242188e-05s
Availability | VoID file availability check for Gene Ontology took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Gene Ontology took 29.164413690567017s
Reputation | Calculation of the PageRank for Gene Ontology took 0.02100825309753418s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008590221405029297s
Believability | Calculation of trust value for Gene Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-go_x2 took 118.03698420524597s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 9.441375732421875e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 31.334085702896118s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.02082347869873047s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.409385681152344e-05s
Believability | Calculation of trust value for Cereal Plant Development took 1.4781951904296875e-05s
INFO | --- Analysis for bioportal-gro took 111.7144706249237s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.506111145019531e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 23.329238891601562s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.021152257919311523s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.00046062469482421875s
Believability | Calculation of trust value for Cereal plant gross anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-gro_x1 took 105.6640112400055s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 34.15718173980713s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.021138906478881836s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007739067077636719s
Believability | Calculation of trust value for Gene Regulation Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-gro_x2 took 210.7012538909912s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 0.00010371208190917969s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.3265800476074219s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.022567033767700195s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.000598907470703125s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hao took 141.36821937561035s
Availability | SPARQL endpoint availability check for HCPCS took 0.00018095970153808594s
Availability | VoID file availability check for HCPCS took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for HCPCS took 24.418504238128662s
Reputation | Calculation of the PageRank for HCPCS took 0.021077871322631836s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00023818016052246094s
Believability | Calculation of trust value for HCPCS took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-hcpcs took 139.19431138038635s
Availability | SPARQL endpoint availability check for Health Level Seven took 9.131431579589844e-05s
Availability | VoID file availability check for Health Level Seven took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for Health Level Seven took 24.804487466812134s
Reputation | Calculation of the PageRank for Health Level Seven took 0.021530866622924805s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012958049774169922s
Believability | Calculation of trust value for Health Level Seven took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-hl7 took 84.78126883506775s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 0.00010395050048828125s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 30.33941650390625s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020894765853881836s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003509521484375s
Believability | Calculation of trust value for HEALTH_INDICATORS took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-hlth_indics took 200.38296389579773s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 9.369850158691406e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 25.8400559425354s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.021131038665771484s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.5762786865234375e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 1.4781951904296875e-05s
INFO | --- Analysis for bioportal-hom took 88.6558268070221s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.792213439941406e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 25.890561819076538s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020870447158813477s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.337860107421875e-05s
Believability | Calculation of trust value for HOM-HARVARD took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-hom_harvard took 137.1546709537506s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 0.00015592575073242188s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 24.64736580848694s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020908832550048828s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006780624389648438s
Believability | Calculation of trust value for Human Phenotype Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hp_x1 took 233.86563873291016s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 9.489059448242188e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 24.544841766357422s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.021471500396728516s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010538101196289062s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-hpio took 134.45093894004822s
Availability | SPARQL endpoint availability check for HUGO took 8.559226989746094e-05s
Availability | VoID file availability check for HUGO took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for HUGO took 0.366471529006958s
Reputation | Calculation of the PageRank for HUGO took 0.020780563354492188s
Interlinking | Calculation of Degree of Connection for HUGO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for HUGO took 9.441375732421875e-05s
Believability | Calculation of trust value for HUGO took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-hugo took 76.74379444122314s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 0.00016069412231445312s
Availability | VoID file availability check for Information Artifact Ontology took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 25.379167079925537s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.02582240104675293s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0008056163787841797s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0007073879241943359s
Believability | Calculation of trust value for Information Artifact Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-iao took 161.054505109787s
Availability | SPARQL endpoint availability check for ICD10 took 4.863739013671875e-05s
Availability | VoID file availability check for ICD10 took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for ICD10 took 24.745927572250366s
Reputation | Calculation of the PageRank for ICD10 took 0.021004199981689453s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008082389831542969s
Believability | Calculation of trust value for ICD10 took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-icd10 took 178.2936191558838s
Availability | SPARQL endpoint availability check for ICD10CM took 9.441375732421875e-05s
Availability | VoID file availability check for ICD10CM took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for ICD10CM took 24.17698645591736s
Reputation | Calculation of the PageRank for ICD10CM took 0.020992755889892578s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006184577941894531s
Believability | Calculation of trust value for ICD10CM took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-icd10cm took 205.12557697296143s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.839897155761719e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 33.44347620010376s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.021036863327026367s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.0001556873321533203s
Believability | Calculation of trust value for ICD-10-PCS took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icd10pcs took 211.5495240688324s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 9.989738464355469e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 24.67538070678711s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.0221860408782959s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006387233734130859s
Believability | Calculation of trust value for International Classification of Diseases took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-icd9cm took 134.2365162372589s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 9.34600830078125e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.317258358001709s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.021069049835205078s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0005900859832763672s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-icf_x1 took 128.3913390636444s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.553794860839844e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 27.090904712677002s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.020969867706298828s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012540817260742188s
Believability | Calculation of trust value for International Classification for Nursing Practice took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-icnp took 190.37013363838196s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 0.0001494884490966797s
Availability | VoID file availability check for International Classification of Primary Care took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 28.438449382781982s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.022201061248779297s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004661083221435547s
Believability | Calculation of trust value for International Classification of Primary Care took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-icpc took 165.63351941108704s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 9.179115295410156e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0006868839263916016s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 28.41827130317688s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020838499069213867s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008599758148193359s
Believability | Calculation of trust value for ICPC-2 PLUS took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-icpc2p took 165.49899816513062s
Availability | SPARQL endpoint availability check for ICPS Network took 9.322166442871094e-05s
Availability | VoID file availability check for ICPS Network took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.30923008918762207s
Reputation | Calculation of the PageRank for ICPS Network took 0.020869970321655273s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0002467632293701172s
Believability | Calculation of trust value for ICPS Network took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-icps took 85.83845615386963s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 9.608268737792969e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.3120415210723877s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020783662796020508s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008325576782226562s
Believability | Calculation of trust value for Infectious Disease Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ido took 109.94397950172424s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.32037854194641113s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.021505117416381836s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011587142944335938s
Believability | Calculation of trust value for Brucellosis Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-idobru took 59.0431649684906s
Availability | SPARQL endpoint availability check for Malaria Ontology took 0.00012373924255371094s
Availability | VoID file availability check for Malaria Ontology took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 29.822608709335327s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.02282881736755371s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013098716735839844s
Believability | Calculation of trust value for Malaria Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-idomal took 192.6387758255005s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.7206878662109375e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 31.63807249069214s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020943164825439453s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.00031876564025878906s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-iev took 168.2218623161316s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.982948303222656e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0003840923309326172s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.3264155387878418s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.021030187606811523s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00017714500427246094s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-imgt took 154.90336346626282s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 6.175041198730469e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0004172325134277344s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 25.872220277786255s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.022325992584228516s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0006296634674072266s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-imr took 183.56879091262817s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 0.00017690658569335938s
Availability | VoID file availability check for Interaction Network Ontology took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 24.80406904220581s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.02093338966369629s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008041858673095703s
Believability | Calculation of trust value for Interaction Network Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ino took 186.04660296440125s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 0.0001518726348876953s
Availability | VoID file availability check for Hewan Invertebrata took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 30.191175937652588s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.021136045455932617s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.409385681152344e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-invertebrata took 116.57190418243408s
Availability | SPARQL endpoint availability check for IxnO took 0.0001125335693359375s
Availability | VoID file availability check for IxnO took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for IxnO took 28.787441968917847s
Reputation | Calculation of the PageRank for IxnO took 0.02116227149963379s
Interlinking | Calculation of Degree of Connection for IxnO took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00021338462829589844s
Believability | Calculation of trust value for IxnO took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ixno took 133.9337763786316s
Availability | SPARQL endpoint availability check for SysMO-JERM took 0.00010132789611816406s
Availability | VoID file availability check for SysMO-JERM took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.31645679473876953s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.021192073822021484s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0004184246063232422s
Believability | Calculation of trust value for SysMO-JERM took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-jerm took 94.14235329627991s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 0.00010251998901367188s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 29.803335666656494s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020806074142456055s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-kisao took 119.08211994171143s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.744529724121094e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 24.795403957366943s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.022075653076171875s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.0002205371856689453s
Believability | Calculation of trust value for Loggerhead nesting took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-lhn took 183.1112823486328s
Availability | SPARQL endpoint availability check for Lipid Ontology took 6.866455078125e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.3128623962402344s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.02334451675415039s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0010950565338134766s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.0002810955047607422s
Believability | Calculation of trust value for Lipid Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-lipro took 26.984538078308105s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.4345855712890625e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 24.72742795944214s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.0210115909576416s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.001875162124633789s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-lnc took 134.6757776737213s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 0.00011539459228515625s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 26.260003328323364s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020807743072509766s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006520748138427734s
Believability | Calculation of trust value for Mouse adult gross anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ma took 114.89831590652466s
Availability | SPARQL endpoint availability check for Multiple alignment took 9.369850158691406e-05s
Availability | VoID file availability check for Multiple alignment took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Multiple alignment took 25.915844440460205s
Reputation | Calculation of the PageRank for Multiple alignment took 0.021056413650512695s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0002117156982421875s
Believability | Calculation of trust value for Multiple alignment took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mao took 180.16475224494934s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 9.489059448242188e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 24.069658756256104s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.021999597549438477s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007030963897705078s
Believability | Calculation of trust value for Minimal anatomical terminology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mat took 222.394202709198s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 0.00011301040649414062s
Availability | VoID file availability check for Breast tissue cell lines took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.35999584197998047s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.02109503746032715s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004534721374511719s
Believability | Calculation of trust value for Breast tissue cell lines took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mcbcc took 165.09872913360596s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.31124162673950195s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020879507064819336s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007655620574951172s
Believability | Calculation of trust value for Cell line ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mccl took 142.64638423919678s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Cell line ontology took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for Cell line ontology took 28.99110221862793s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02126455307006836s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0015118122100830078s
Believability | Calculation of trust value for Cell line ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 162.64865374565125s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 0.00011038780212402344s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 27.84069013595581s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.022574901580810547s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002570152282714844s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mcv took 189.10484313964844s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 6.0558319091796875e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0004131793975830078s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 30.034549236297607s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020993947982788086s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00018596649169921875s
Believability | Calculation of trust value for Master Drug Data Base took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mddb took 142.53890562057495s
Availability | SPARQL endpoint availability check for MedDRA took 4.887580871582031e-05s
Availability | VoID file availability check for MedDRA took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for MedDRA took 0.4533665180206299s
Reputation | Calculation of the PageRank for MedDRA took 0.02131032943725586s
Interlinking | Calculation of Degree of Connection for MedDRA took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0008914470672607422s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0012540817260742188s
Believability | Calculation of trust value for MedDRA took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mdr took 96.58602690696716s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 5.1021575927734375e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.00037097930908203125s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.30217409133911133s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.022182703018188477s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0010824203491210938s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0010840892791748047s
Believability | Calculation of trust value for MedlinePlus Health Topics took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-medlineplus took 54.33218479156494s
Availability | SPARQL endpoint availability check for MeGO took 4.9114227294921875e-05s
Availability | VoID file availability check for MeGO took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for MeGO took 0.3092682361602783s
Reputation | Calculation of the PageRank for MeGO took 0.02245473861694336s
Interlinking | Calculation of Degree of Connection for MeGO took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00015807151794433594s
Believability | Calculation of trust value for MeGO took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mego took 80.72159004211426s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 9.846687316894531e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 25.804593563079834s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.021043777465820312s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018491744995117188s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-mesh-owl took 109.03293371200562s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 9.250640869140625e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.3559236526489258s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.021004915237426758s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006442070007324219s
Believability | Calculation of trust value for Mental Functioning Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mf took 155.84994626045227s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 9.393692016601562e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 27.757502794265747s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020898818969726562s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005753040313720703s
Believability | Calculation of trust value for Medaka fish anatomy and development took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mfo took 205.54199171066284s
Availability | SPARQL endpoint availability check for Emotion Ontology took 9.179115295410156e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 30.120364665985107s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.0210263729095459s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007898807525634766s
Believability | Calculation of trust value for Emotion Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mfoem took 248.98148560523987s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 0.0001010894775390625s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.41747355461120605s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.022277355194091797s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0008094310760498047s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.0001518726348876953s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mhc took 166.2388129234314s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 9.846687316894531e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.40659022331237793s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.021401405334472656s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0007162094116210938s
Believability | Calculation of trust value for Protein-protein interaction took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mi took 35.25163412094116s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 0.00010037422180175781s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.29976844787597656s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020984411239624023s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007226467132568359s
Believability | Calculation of trust value for Mosquito insecticide resistance took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-miro took 142.38392543792725s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 0.00010132789611816406s
Availability | VoID file availability check for Measurement Method Ontology took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 29.94601845741272s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.02119731903076172s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.000823974609375s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.000171661376953125s
Believability | Calculation of trust value for Measurement Method Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mmo took 227.1830439567566s
Availability | SPARQL endpoint availability check for MGED Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for MGED Ontology took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.3071861267089844s
Reputation | Calculation of the PageRank for MGED Ontology took 0.021574020385742188s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0004246234893798828s
Believability | Calculation of trust value for MGED Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mo took 89.62360119819641s
Availability | SPARQL endpoint availability check for Protein modification took 0.00010824203491210938s
Availability | VoID file availability check for Protein modification took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for Protein modification took 0.3161900043487549s
Reputation | Calculation of the PageRank for Protein modification took 0.021521806716918945s
Interlinking | Calculation of Degree of Connection for Protein modification took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002429485321044922s
Believability | Calculation of trust value for Protein modification took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mod took 138.54483222961426s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.935264587402344e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 26.301737308502197s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.02223038673400879s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0010311603546142578s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0008370876312255859s
Believability | Calculation of trust value for Mammalian phenotype took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mp took 133.65486073493958s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.839897155761719e-05s
Availability | VoID file availability check for Mouse pathology took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.32366442680358887s
Reputation | Calculation of the PageRank for Mouse pathology took 0.021106243133544922s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0005166530609130859s
Believability | Calculation of trust value for Mouse pathology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mpath took 159.0736961364746s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.982948303222656e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.32010960578918457s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.0213165283203125s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0008528232574462891s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0004677772521972656s
Believability | Calculation of trust value for Mass spectrometry took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ms took 161.92423510551453s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 9.608268737792969e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.3228030204772949s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.02101445198059082s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0019404888153076172s
Believability | Calculation of trust value for Medical Subject Headings took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-msh took 129.14595413208008s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 9.989738464355469e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.3977327346801758s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020955801010131836s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.0001819133758544922s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mthch took 193.4310359954834s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.935264587402344e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 27.173571586608887s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.02087116241455078s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007963180541992188s
Believability | Calculation of trust value for Natural Products Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-natpro took 199.53202438354492s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 9.703636169433594e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 26.503101348876953s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.022147178649902344s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008244514465332031s
Believability | Calculation of trust value for NCBI organismal classification took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 112.58812499046326s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 9.489059448242188e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.35864782333374023s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020926952362060547s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0020046234130859375s
Believability | Calculation of trust value for NCI Thesaurus took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ncit took 88.07944202423096s
Availability | SPARQL endpoint availability check for National Drug Data File took 0.00010013580322265625s
Availability | VoID file availability check for National Drug Data File took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for National Drug Data File took 32.74439764022827s
Reputation | Calculation of the PageRank for National Drug Data File took 0.0317082405090332s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0014410018920898438s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0009918212890625s
Believability | Calculation of trust value for National Drug Data File took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-nddf took 176.26829624176025s
Availability | SPARQL endpoint availability check for National Drug File took 4.9114227294921875e-05s
Availability | VoID file availability check for National Drug File took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for National Drug File took 0.27696800231933594s
Reputation | Calculation of the PageRank for National Drug File took 0.02122664451599121s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012812614440917969s
Believability | Calculation of trust value for National Drug File took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ndfrt took 193.24471282958984s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 9.417533874511719e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.3766489028930664s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02236175537109375s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.001161336898803711s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0013682842254638672s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 88.05754590034485s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 9.417533874511719e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 25.670326948165894s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.021472692489624023s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0007283687591552734s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-neomark took 138.95745420455933s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 0.00011324882507324219s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0006461143493652344s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 29.36434054374695s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.022495508193969727s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0009012222290039062s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.0001609325408935547s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-neomarkontology took 171.89464116096497s
Availability | SPARQL endpoint availability check for NIFSTD took 0.00011396408081054688s
Availability | VoID file availability check for NIFSTD took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for NIFSTD took 26.957814931869507s
Reputation | Calculation of the PageRank for NIFSTD took 0.02266407012939453s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0019249916076660156s
Believability | Calculation of trust value for NIFSTD took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-nif took 144.39898014068604s
Availability | SPARQL endpoint availability check for NIF Cell took 4.744529724121094e-05s
Availability | VoID file availability check for NIF Cell took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.29003095626831055s
Reputation | Calculation of the PageRank for NIF Cell took 0.021434545516967773s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013523101806640625s
Believability | Calculation of trust value for NIF Cell took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-nif_cell took 118.17074632644653s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.5299530029296875e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.3553276062011719s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.0210421085357666s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014712810516357422s
Believability | Calculation of trust value for NIF Dysfunction took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 109.64630150794983s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 5.507469177246094e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.3069314956665039s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.021573781967163086s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0010883808135986328s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0007331371307373047s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-nigo took 169.73768520355225s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.76837158203125e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 27.745744943618774s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.02171158790588379s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005922317504882812s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-nmr took 166.84182286262512s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 5.53131103515625e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.2895991802215576s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.022516727447509766s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00013208389282226562s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nonrctontology took 177.01161289215088s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 5.054473876953125e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.30873775482177734s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.02273249626159668s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0011610984802246094s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0013794898986816406s
Believability | Calculation of trust value for NanoParticle Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-npo took 146.2248318195343s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 9.34600830078125e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 27.75478720664978s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.022884607315063477s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0008287429809570312s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-oae took 144.07871055603027s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 9.274482727050781e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.3606407642364502s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.021651744842529297s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.000997304916381836s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.001631021499633789s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-obi took 136.53317642211914s
Availability | SPARQL endpoint availability check for OBOE took 9.012222290039062e-05s
Availability | VoID file availability check for OBOE took 0.0003924369812011719s
Completeness | Calculation of interlinking completeness for OBOE took 24.801701068878174s
Reputation | Calculation of the PageRank for OBOE took 0.02107977867126465s
Interlinking | Calculation of Degree of Connection for OBOE took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0008945465087890625s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.0001399517059326172s
Believability | Calculation of trust value for OBOE took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-oboe took 85.7246446609497s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.982948303222656e-05s
Availability | VoID file availability check for OBOE SBC took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for OBOE SBC took 25.50275754928589s
Reputation | Calculation of the PageRank for OBOE SBC took 0.021204710006713867s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0008590221405029297s
Believability | Calculation of trust value for OBOE SBC took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 168.2971920967102s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 5.412101745605469e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.3316023349761963s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.02107858657836914s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005939006805419922s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ocre took 83.6234393119812s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 0.00010085105895996094s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.3145277500152588s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020827293395996094s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008714199066162109s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-odgi took 65.03913903236389s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 9.465217590332031e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 25.877722024917603s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.021752357482910156s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0010373592376708984s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.001039266586303711s
Believability | Calculation of trust value for Ontology for Genetic Interval took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ogi took 242.95197939872742s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 0.00012183189392089844s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 25.19802975654602s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.021589040756225586s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0008985996246337891s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00038170814514160156s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ogmd took 137.84532761573792s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 9.5367431640625e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 30.225747108459473s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.021265029907226562s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006742477416992188s
Believability | Calculation of trust value for Ontology for General Medical Science took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ogms took 113.08685827255249s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 0.00010704994201660156s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.31401705741882324s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.0222625732421875s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0009844303131103516s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.001308441162109375s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-omim took 138.55897855758667s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 9.393692016601562e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.28928112983703613s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020833969116210938s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.00037670135498046875s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-omit took 82.05655431747437s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.744529724121094e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 29.666733503341675s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020964384078979492s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006170272827148438s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-omrse took 194.2413947582245s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 9.489059448242188e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 27.99979329109192s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.02170872688293457s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0009975433349609375s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.00091552734375s
Believability | Calculation of trust value for Ontology of Data Mining took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ontodm took 108.81900906562805s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.482269287109375e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 28.373847723007202s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.021303892135620117s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0008270740509033203s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002741813659667969s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ontodt took 112.30526685714722s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.57763671875e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 31.375670194625854s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006270408630371094s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ontoorpha took 182.8153841495514s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 6.628036499023438e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.31279516220092773s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.021532773971557617s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009734630584716797s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-opl took 88.41812372207642s
Availability | SPARQL endpoint availability check for Phenotypic quality took 5.4836273193359375e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.38736844062805176s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.021125316619873047s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0009069442749023438s
Believability | Calculation of trust value for Phenotypic quality took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pato took 95.48904490470886s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.4345855712890625e-05s
Availability | VoID file availability check for Physician Data Query took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.29014134407043457s
Reputation | Calculation of the PageRank for Physician Data Query took 0.021712779998779297s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0007946491241455078s
Believability | Calculation of trust value for Physician Data Query took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pdq took 154.42895603179932s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.649162292480469e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.32256031036376953s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.021355390548706055s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008206367492675781s
Believability | Calculation of trust value for Pediatric Terminology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pedterm took 29.873210668563843s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 25.46683979034424s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.022000789642333984s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.0002224445343017578s
Believability | Calculation of trust value for Parasite Experiment Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-peo took 169.2426118850708s
Availability | SPARQL endpoint availability check for PHARE took 9.202957153320312e-05s
Availability | VoID file availability check for PHARE took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for PHARE took 0.34246039390563965s
Reputation | Calculation of the PageRank for PHARE took 0.021893024444580078s
Interlinking | Calculation of Degree of Connection for PHARE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006287097930908203s
Believability | Calculation of trust value for PHARE took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-phare took 107.77191376686096s
Availability | SPARQL endpoint availability check for PKO_Re took 0.00010728836059570312s
Availability | VoID file availability check for PKO_Re took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.3008596897125244s
Reputation | Calculation of the PageRank for PKO_Re took 0.02126598358154297s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00018930435180664062s
Believability | Calculation of trust value for PKO_Re took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pko took 81.73682475090027s
Availability | SPARQL endpoint availability check for PMA 2010 took 0.0001010894775390625s
Availability | VoID file availability check for PMA 2010 took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.3435328006744385s
Reputation | Calculation of the PageRank for PMA 2010 took 0.023241519927978516s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0009748935699462891s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0010557174682617188s
Believability | Calculation of trust value for PMA 2010 took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pma took 183.8022174835205s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.696846008300781e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.3027842044830322s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.023093461990356445s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0011506080627441406s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.000274658203125s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-pmr took 109.8767306804657s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.482269287109375e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.32608962059020996s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00038933753967285156s
Believability | Calculation of trust value for Plant Anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-po took 171.30970168113708s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 9.942054748535156e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.35455870628356934s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.02113032341003418s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 7.081031799316406e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-po_x1 took 115.86185002326965s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Plant Ontology took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for Plant Ontology took 29.145859718322754s
Reputation | Calculation of the PageRank for Plant Ontology took 0.02099013328552246s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.000446319580078125s
Believability | Calculation of trust value for Plant Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-po_x2 took 202.406231880188s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 9.274482727050781e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.34528136253356934s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.022785425186157227s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0008232593536376953s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0007162094116210938s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-pr took 30.780876874923706s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.38690185546875e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 29.689217567443848s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.021004438400268555s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00028777122497558594s
Believability | Calculation of trust value for Proteomics data and process provenance took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-propreo took 169.81784963607788s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Pathway ontology took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Pathway ontology took 29.702241897583008s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020862340927124023s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00013637542724609375s
Believability | Calculation of trust value for Pathway ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pw took 142.3813192844391s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 9.965896606445312e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.3217167854309082s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.022709131240844727s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0009851455688476562s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 5.054473876953125e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-qibo took 195.491060256958s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.935264587402344e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.00030422210693359375s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.4176151752471924s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02129840850830078s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0018787384033203125s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-rcd took 83.60384559631348s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 9.298324584960938e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.3138449192047119s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02184009552001953s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00016188621520996094s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-rctontology took 118.82891154289246s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 9.179115295410156e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 31.99211311340332s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.021518468856811523s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0009350776672363281s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 0.0001270771026611328s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-repo took 88.19338512420654s
Availability | SPARQL endpoint availability check for Physico-chemical process took 0.00014710426330566406s
Availability | VoID file availability check for Physico-chemical process took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.3006248474121094s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020798444747924805s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0008366107940673828s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.0002300739288330078s
Believability | Calculation of trust value for Physico-chemical process took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-rex took 91.65629148483276s
Availability | SPARQL endpoint availability check for RadLex took 9.059906005859375e-05s
Availability | VoID file availability check for RadLex took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for RadLex took 0.3282601833343506s
Reputation | Calculation of the PageRank for RadLex took 0.02542710304260254s
Interlinking | Calculation of Degree of Connection for RadLex took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0016438961029052734s
Believability | Calculation of trust value for RadLex took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-rid took 137.63164281845093s
Availability | SPARQL endpoint availability check for RNA ontology took 0.00015497207641601562s
Availability | VoID file availability check for RNA ontology took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.3319814205169678s
Reputation | Calculation of the PageRank for RNA ontology took 0.02141857147216797s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005776882171630859s
Believability | Calculation of trust value for RNA ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-rnao took 84.6217532157898s
Availability | SPARQL endpoint availability check for Role Ontology took 6.318092346191406e-05s
Availability | VoID file availability check for Role Ontology took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Role Ontology took 26.32649874687195s
Reputation | Calculation of the PageRank for Role Ontology took 0.021374940872192383s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0008261203765869141s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00025010108947753906s
Believability | Calculation of trust value for Role Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-roleo took 110.04240775108337s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 0.00010848045349121094s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.3002285957336426s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.02237248420715332s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00020432472229003906s
Believability | Calculation of trust value for Rat Strain Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-rs took 165.8168807029724s
Availability | SPARQL endpoint availability check for RxNORM took 0.00011801719665527344s
Availability | VoID file availability check for RxNORM took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for RxNORM took 0.3268284797668457s
Reputation | Calculation of the PageRank for RxNORM took 0.021057605743408203s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006222724914550781s
Believability | Calculation of trust value for RxNORM took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-rxnorm took 84.47925996780396s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 0.00010848045349121094s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 23.49896264076233s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0011065006256103516s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-sao took 208.12789011001587s
Availability | SPARQL endpoint availability check for Systems Biology took 0.00016379356384277344s
Availability | VoID file availability check for Systems Biology took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.33588576316833496s
Reputation | Calculation of the PageRank for Systems Biology took 0.021367788314819336s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004963874816894531s
Believability | Calculation of trust value for Systems Biology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sbo took 117.96686339378357s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 0.00011396408081054688s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.3124408721923828s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.020923614501953125s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00011444091796875s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-sbro took 83.1190254688263s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 0.00011205673217773438s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.33248472213745117s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.02119135856628418s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013277530670166016s
Believability | Calculation of trust value for Sleep Domain Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sdo took 180.40106892585754s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.7206878662109375e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.31149792671203613s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02234196662902832s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00036787986755371094s
Believability | Calculation of trust value for Sample processing and separation techniques took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sep took 105.73427653312683s
Availability | SPARQL endpoint availability check for Student Health Record took 4.673004150390625e-05s
Availability | VoID file availability check for Student Health Record took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Student Health Record took 30.17802381515503s
Reputation | Calculation of the PageRank for Student Health Record took 0.021129131317138672s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.00046062469482421875s
Believability | Calculation of trust value for Student Health Record took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-shr took 199.15279507637024s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 26.64301347732544s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.021610498428344727s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012595653533935547s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sio took 111.65256762504578s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 9.226799011230469e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 30.087661743164062s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.02099919319152832s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.0002200603485107422s
Believability | Calculation of trust value for Situation-Based Access Control took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sitbac took 116.62038898468018s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.649162292480469e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.42407727241516113s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.022353649139404297s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.52587890625e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0008208751678466797s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.002046346664428711s
Believability | Calculation of trust value for SNOMED Clinical Terms took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-snomedct took 142.49016451835632s
Availability | SPARQL endpoint availability check for SNP-Ontology took 9.34600830078125e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.29973745346069336s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020973920822143555s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006899833679199219s
Believability | Calculation of trust value for SNP-Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-snpo took 56.392425775527954s
Availability | SPARQL endpoint availability check for Sequence types and features took 0.00010204315185546875s
Availability | VoID file availability check for Sequence types and features took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.295790433883667s
Reputation | Calculation of the PageRank for Sequence types and features took 0.02172064781188965s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0011067390441894531s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0007224082946777344s
Believability | Calculation of trust value for Sequence types and features took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-so_x1 took 180.0514998435974s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 9.226799011230469e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 28.378664255142212s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.023056507110595703s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015873908996582031s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sopharm took 112.15994548797607s
Availability | SPARQL endpoint availability check for SoyOntology took 5.030632019042969e-05s
Availability | VoID file availability check for SoyOntology took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for SoyOntology took 27.59057927131653s
Reputation | Calculation of the PageRank for SoyOntology took 0.021794795989990234s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0009353160858154297s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00016832351684570312s
Believability | Calculation of trust value for SoyOntology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-soy took 136.9707911014557s
Availability | SPARQL endpoint availability check for Spider Ontology took 9.560585021972656e-05s
Availability | VoID file availability check for Spider Ontology took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Spider Ontology took 25.407145261764526s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020893573760986328s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003390312194824219s
Believability | Calculation of trust value for Spider Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-spd took 112.65647983551025s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 5.5789947509765625e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.32668423652648926s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.022591352462768555s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00030541419982910156s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-spto took 87.29851794242859s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 9.274482727050781e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.32862162590026855s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.020972251892089844s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0005025863647460938s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sso took 59.962671518325806s
Availability | SPARQL endpoint availability check for Software Ontology took 4.744529724121094e-05s
Availability | VoID file availability check for Software Ontology took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.4373660087585449s
Reputation | Calculation of the PageRank for Software Ontology took 0.022637367248535156s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0010967254638671875s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0005369186401367188s
Believability | Calculation of trust value for Software Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-swo took 147.36269235610962s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 0.00010085105895996094s
Availability | VoID file availability check for Tick gross anatomy took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 24.842499494552612s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.021231651306152344s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002689361572265625s
Believability | Calculation of trust value for Tick gross anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-tads took 143.38572669029236s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 9.632110595703125e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.320969820022583s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.022702455520629883s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0010192394256591797s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0010721683502197266s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-tao took 143.59262704849243s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.696846008300781e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.31137585639953613s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.021160364151000977s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0008137226104736328s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 0.00011181831359863281s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-taxrank took 136.68461227416992s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 5.078315734863281e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.3206770420074463s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.02142477035522461s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 8.225440979003906e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-teddy took 141.15420055389404s
Availability | SPARQL endpoint availability check for Time Event Ontology took 5.7220458984375e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 26.022135972976685s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020966291427612305s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.00086212158203125s
Believability | Calculation of trust value for Time Event Ontology took 1.5020370483398438e-05s
INFO | --- Analysis for bioportal-teo took 197.35808658599854s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 9.059906005859375e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0003871917724609375s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 29.129055500030518s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.02090764045715332s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00044655799865722656s
Believability | Calculation of trust value for Mosquito gross anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-tgma took 114.44480729103088s
Availability | SPARQL endpoint availability check for thesaurus took 9.965896606445312e-05s
Availability | VoID file availability check for thesaurus took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for thesaurus took 30.3530433177948s
Reputation | Calculation of the PageRank for thesaurus took 0.020890474319458008s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for thesaurus took 8.368492126464844e-05s
Believability | Calculation of trust value for thesaurus took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-thesaurus took 144.1394965648651s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.482269287109375e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.00038361549377441406s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 30.600965976715088s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.02344226837158203s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0010607242584228516s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.00044798851013183594s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 144.5670075416565s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.935264587402344e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0003218650817871094s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.3044857978820801s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.022870302200317383s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008640289306640625s
Believability | Calculation of trust value for Translational Medicine Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-tmo took 138.6587791442871s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 26.804279327392578s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.022673845291137695s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00018668174743652344s
Believability | Calculation of trust value for Plant Trait Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-to took 171.56173825263977s
Availability | SPARQL endpoint availability check for TOK_Ontology took 5.1021575927734375e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 29.749043226242065s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.02199554443359375s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00021266937255859375s
Believability | Calculation of trust value for TOK_Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-tok took 176.288161277771s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 8.988380432128906e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 28.420519590377808s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020886659622192383s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0010821819305419922s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.0002772808074951172s
Believability | Calculation of trust value for Teleost taxonomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tto took 111.82191061973572s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 5.1021575927734375e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0003497600555419922s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 26.185925245285034s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.021178722381591797s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.001041412353515625s
Believability | Calculation of trust value for Uber anatomy ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-uberon took 188.1549506187439s
Availability | SPARQL endpoint availability check for Units Ontology took 9.226799011230469e-05s
Availability | VoID file availability check for Units Ontology took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Units Ontology took 25.47335147857666s
Reputation | Calculation of the PageRank for Units Ontology took 0.021491527557373047s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002493858337402344s
Believability | Calculation of trust value for Units Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-unitsontology took 136.32014298439026s
Availability | SPARQL endpoint availability check for Units of measurement took 4.673004150390625e-05s
Availability | VoID file availability check for Units of measurement took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for Units of measurement took 29.005269765853882s
Reputation | Calculation of the PageRank for Units of measurement took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00029468536376953125s
Believability | Calculation of trust value for Units of measurement took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-uo took 168.00584530830383s
Availability | SPARQL endpoint availability check for VANDF took 4.5299530029296875e-05s
Availability | VoID file availability check for VANDF took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for VANDF took 29.07880926132202s
Reputation | Calculation of the PageRank for VANDF took 0.02099013328552246s
Interlinking | Calculation of Degree of Connection for VANDF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0008406639099121094s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007328987121582031s
Believability | Calculation of trust value for VANDF took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-vandf took 141.4541792869568s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 9.107589721679688e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 25.707629442214966s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.021247386932373047s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0005040168762207031s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-vao took 194.57884740829468s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 7.176399230957031e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 24.102490186691284s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.021960973739624023s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0008397102355957031s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0007927417755126953s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-vhog took 107.91965246200562s
Availability | SPARQL endpoint availability check for VIVO took 0.000102996826171875s
Availability | VoID file availability check for VIVO took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for VIVO took 0.3553304672241211s
Reputation | Calculation of the PageRank for VIVO took 0.02091526985168457s
Interlinking | Calculation of Degree of Connection for VIVO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003662109375s
Believability | Calculation of trust value for VIVO took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-vivo took 117.4310691356659s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 28.00277018547058s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.021201372146606445s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 5.817413330078125e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0008370876312255859s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0013930797576904297s
Believability | Calculation of trust value for Vaccine Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-vo took 191.58434772491455s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 0.00010466575622558594s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.30057859420776367s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.021005868911743164s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.0002453327178955078s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-vt took 119.12153458595276s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.887580871582031e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.298173189163208s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.021007537841796875s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0004999637603759766s
Believability | Calculation of trust value for C. elegans gross anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-wbbt took 175.2150523662567s
Availability | SPARQL endpoint availability check for C. elegans development took 4.458427429199219e-05s
Availability | VoID file availability check for C. elegans development took 0.0003724098205566406s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.33312392234802246s
Reputation | Calculation of the PageRank for C. elegans development took 0.021240949630737305s
Interlinking | Calculation of Degree of Connection for C. elegans development took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 5.245208740234375e-05s
Believability | Calculation of trust value for C. elegans development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-wbls took 197.36277103424072s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.410743713378906e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 28.824679374694824s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.021038055419921875s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 0.00010371208190917969s
Believability | Calculation of trust value for C. elegans phenotype took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-wbphenotype took 174.89693140983582s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 9.775161743164062e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 25.449503421783447s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.021210193634033203s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006124973297119141s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-who took 139.85821723937988s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 9.202957153320312e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.314807653427124s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.02097797393798828s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0007066726684570312s
Believability | Calculation of trust value for Xenopus anatomy and development took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-xao took 90.93919491767883s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 0.00011515617370605469s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 29.2082622051239s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.021964073181152344s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0009715557098388672s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.0003254413604736328s
Believability | Calculation of trust value for Experimental Conditions Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-xco took 139.0516288280487s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.649162292480469e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.3065037727355957s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020957231521606445s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002903938293457031s
Believability | Calculation of trust value for Yeast phenotypes took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ypo took 113.65738201141357s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 0.00016236305236816406s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 27.932148218154907s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.02118372917175293s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007491111755371094s
Believability | Calculation of trust value for Zebrafish anatomy and development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-zfa took 58.58001470565796s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.673004150390625e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 29.695698976516724s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020999670028686523s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 4.1961669921875e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.1444091796875e-05s
INFO | --- Analysis for Bioportal_link took 168.88003730773926s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.6052901744842529s
Availability | VoID file availability check for BioSamples RDF took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.29968810081481934s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.02192831039428711s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 4.38690185546875e-05s
Believability | Calculation of trust value for BioSamples RDF took 2.4318695068359375e-05s
INFO | --- Analysis for biosamples-rdf took 145.01943182945251s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.10225200653076172s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 26.21591281890869s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.028510332107543945s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0014543533325195312s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00017595291137695312s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.239776611328125e-05s
INFO | --- Analysis for bis-linked-data took 114.9535140991211s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.00011157989501953125s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 24.342479944229126s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.021324634552001953s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.315376281738281e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for bll-thesaurus took 112.83172273635864s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.0072307586669922s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 29.066559076309204s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.021175384521484375s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 8.106231689453125e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for bluk-bnb took 196.30376291275024s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.21495532989501953s
Availability | VoID file availability check for Thesaurus BNCF took 0.0007379055023193359s
Extra | Recovery of all triples for Thesaurus BNCF took 44.67495512962341s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6070766448974609s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6104221343994141s
Interoperability | New terms check for Thesaurus BNCF took 1.6005971431732178s
Versatility | Languages check for Thesaurus BNCF took 6.753070592880249s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.7863211631774902s
Security | Check HTTPS for Thesaurus BNCF took 0.07158136367797852s
Interpretability | RDF structures check for Thesaurus BNCF took 0.13104605674743652s
Versatility | Serialization formats check for Thesaurus BNCF took 0.1256425380706787s
Availability | RDF dump link check for Thesaurus BNCF took 0.13028550148010254s
License | MR license check for Thesaurus BNCF took 0.12357306480407715s
License | HR license check for Thesaurus BNCF took 1.214001178741455s
Amount of data | Number of property check for Thesaurus BNCF took 0.13323068618774414s
Understandability | Number of label check for Thesaurus BNCF took 0.27890753746032715s
Understandability | URI regex check for Thesaurus BNCF took 0.5361955165863037s
Understandability | Vocabs check for Thesaurus BNCF took 0.14014101028442383s
Verifiability | Authors check for Thesaurus BNCF took 0.2270209789276123s
Verifiability | Publishers check for Thesaurus BNCF took 0.13234925270080566s
Performance | Throughput check for Thesaurus BNCF took 13.583949327468872s
Amount of data | Check the number of entities for Thesaurus BNCF took 9.34600830078125e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.13429880142211914s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.15060019493103027s
Interlinking | skos check for Thesaurus BNCF took 0.177870512008667s
Interlinking | skos check for Thesaurus BNCF took 0.350750207901001s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.13462352752685547s
Currency | Creation date check for Thesaurus BNCF took 0.27451562881469727s
Currency | Modification date check for Thesaurus BNCF took 0.2817409038543701s
Rep.Conc. | URIs length for Thesaurus BNCF took 26.403892040252686s
Interoperability | New vocabularies check for Thesaurus BNCF took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.18747830390930176s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.11431622505187988s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.12336611747741699s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 13.258407592773438s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.49924397468566895s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.9922680854797363s
Consistency | Disjoint class check for Thesaurus BNCF took 0.15962743759155273s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.8999052047729492s
Consistency | Misplaced classes for Thesaurus BNCF took 6.8514697551727295s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 8.294962882995605s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.6048860549926758s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.3175928592681885s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.466369867324829s
Security | Sign check for Thesaurus BNCF took 0.1476271152496338s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 20.865538597106934s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.3560934066772461s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.021138429641723633s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0009701251983642578s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 9.369850158691406e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 2.1457672119140625e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 1.2636184692382812e-05s
INFO | --- Analysis for bncf-ns took 374.6141285896301s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5350465774536133s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007767677307128906s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8695347309112549s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9101781845092773s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.555393695831299s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.179601192474365s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.24366068840027s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.822441577911377s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.32664990425109863s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3884098529815674s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4352443218231201s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.37935519218444824s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3701601028442383s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.2447247505188s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.416424036026001s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5635740756988525s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7794308662414551s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3479311466217041s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4070932865142822s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35301780700683594s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.799633979797363s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.557868957519531e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3713231086730957s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3559737205505371s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38258886337280273s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38847994804382324s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4513387680053711s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6416878700256348s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.291032075881958s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 17.161255359649658s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.37300992012023926s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3553016185760498s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3715646266937256s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8346683979034424s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.023879289627075195s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030319929122924805s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.42101478576660156s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.973597288131714s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5024242401123047s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.539064645767212s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8209929466247559s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.394997358322144s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03285527229309082s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4033668041229248s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3672304153442383s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 10.877051591873169s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 27.340807676315308s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.022726058959960938s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.771087646484375e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1920928955078125e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.2874603271484375e-05s
INFO | --- Analysis for bpr took 560.4531018733978s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 0.000156402587890625s
Availability | VoID file availability check for Brazilian Politicians took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.29897522926330566s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.021242856979370117s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.891654968261719e-05s
Believability | Calculation of trust value for Brazilian Politicians took 9.5367431640625e-06s
INFO | --- Analysis for brazilian-politicians took 132.25555777549744s
Availability | SPARQL endpoint availability check for Bricklink took 2.7498722076416016s
Availability | VoID file availability check for Bricklink took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Bricklink took 0.3274085521697998s
Reputation | Calculation of the PageRank for Bricklink took 0.021660327911376953s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Bricklink took 7.367134094238281e-05s
Believability | Calculation of trust value for Bricklink took 1.2159347534179688e-05s
INFO | --- Analysis for bricklink took 105.33124899864197s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.113524198532104s
Availability | VoID file availability check for British Museum Collection took 0.0007171630859375s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.30042243003845215s
Reputation | Calculation of the PageRank for British Museum Collection took 0.021287918090820312s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 4.029273986816406e-05s
Believability | Calculation of trust value for British Museum Collection took 1.3589859008789062e-05s
INFO | --- Analysis for british-museum-collection took 165.1749885082245s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 0.00011134147644042969s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.321242094039917s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.021024465560913086s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.3392181396484375e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.1920928955078125e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 30.386704206466675s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24864602088928223s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006654262542724609s
Extra | Recovery of all triples for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 11.684738397598267s
Performance | Total latancy measurement for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.6195917129516602s
Amount of data | Number of triples check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.0578582286834717s
Interoperability | New terms check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.988619327545166s
Versatility | Languages check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.151283502578735s
Interpretability | Number of blank nodes check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.8829944133758545s
Interpretability | RDF structures check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12344622611999512s
Versatility | Serialization formats check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12313294410705566s
Availability | RDF dump link check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12078976631164551s
License | MR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1292722225189209s
License | HR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 16.140126705169678s
Amount of data | Number of property check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12099146842956543s
Understandability | Number of label check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.16975069046020508s
Understandability | URI regex check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24042487144470215s
Understandability | Vocabs check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12859296798706055s
Verifiability | Authors check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12137174606323242s
Verifiability | Publishers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1214895248413086s
Performance | Throughput check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.838139772415161s
Amount of data | Check the number of entities for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.581710815429688e-05s
Verifiability | Contribs. check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12155389785766602s
Interlinking | sameAs chians check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1207270622253418s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11366677284240723s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11397027969360352s
Timeliness | dataset update frequency check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12163209915161133s
Currency | Creation date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2504549026489258s
Currency | Modification date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24912309646606445s
Rep.Conc. | URIs length for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.77443814277649s
Interoperability | New vocabularies check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12259292602539062s
Accuracy | Check Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11327958106994629s
Accuracy | Check Inverse Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1205606460571289s
Accuracy | Check Empty annotation labels for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.245957612991333s
Accuracy | Check White space in annotation for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24643445014953613s
Accuracy | Check Datatype consistency for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.631754636764526s
Consistency | Disjoint class check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1231696605682373s
Consistency | Check Misplaced properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.152806282043457s
Consistency | Check Ontology hijacking for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.493396282196045s
Consistency | Check Invalid usage of undefined classes for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.4131484031677246s
Consistency | Check Invalid usage of undefined properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.505190372467041s
Conciseness | Check Extensional conciseness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.78889536857605s
Security | Sign check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12076759338378906s
Availability | Check URIs Dereferenciability for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3608.006178379059s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 29.284101009368896s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.02144455909729004s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.5272369384765625e-05s
Interoperability | Check the re-using of existing vocabs for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.9073486328125e-06s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3828277587890625e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 3828.329501390457s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.24047636985778809s
Availability | VoID file availability check for business.data.gov.uk took 0.0003409385681152344s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 25.2052161693573s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.022161245346069336s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0012927055358886719s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 7.200241088867188e-05s
Believability | Calculation of trust value for business.data.gov.uk took 5.4836273193359375e-06s
INFO | --- Analysis for business-data-gov-uk took 161.8532645702362s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.48653125762939453s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0004401206970214844s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 2.4517955780029297s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.4891395568847656s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.38626813888549805s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.7433738708496094s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 39.94751000404358s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.3431582450866699s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.18867993354797363s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.2968578338623047s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.3006258010864258s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.3220250606536865s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.31758785247802734s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 11.861671209335327s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.29508185386657715s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.33237314224243164s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.6055021286010742s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.2859923839569092s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.31545448303222656s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.2978193759918213s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 12.417854309082031s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 5.364418029785156e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.30052781105041504s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.31873321533203125s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3130214214324951s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.30701637268066406s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.28952455520629883s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.6116902828216553s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.598684549331665s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 4.908196687698364s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.3084242343902588s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.37515902519226074s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.360245943069458s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.7908430099487305s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.031789541244506836s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.02958822250366211s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.4126412868499756s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.4368994235992432s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.39583873748779297s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.9641189575195312s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.3732085227966309s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.5015456676483154s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03384709358215332s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.3119933605194092s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.30522632598876953s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1425.9885456562042s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 31.892974376678467s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.021342992782592773s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-05s
INFO | --- Analysis for BVMC took 1721.1935002803802s
Availability | SPARQL endpoint availability check for cablegate took 1.6285502910614014s
Availability | VoID file availability check for cablegate took 0.0007331371307373047s
Completeness | Calculation of interlinking completeness for cablegate took 0.3016045093536377s
Reputation | Calculation of the PageRank for cablegate took 0.021131038665771484s
Interlinking | Calculation of Degree of Connection for cablegate took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for cablegate took 7.82012939453125e-05s
Believability | Calculation of trust value for cablegate took 1.239776611328125e-05s
INFO | --- Analysis for cablegate took 16.98636531829834s
Availability | SPARQL endpoint availability check for Calames took 4.839897155761719e-05s
Availability | VoID file availability check for Calames took 0.0011026859283447266s
Completeness | Calculation of interlinking completeness for Calames took 0.31018900871276855s
Reputation | Calculation of the PageRank for Calames took 0.021293163299560547s
Interlinking | Calculation of Degree of Connection for Calames took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Calames took 0.0008647441864013672s
Interlinking | Calculation of Clustering coefficient for Calames took 4.291534423828125e-05s
Believability | Calculation of trust value for Calames took 1.3113021850585938e-05s
INFO | --- Analysis for calames took 117.01320433616638s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.37976956367492676s
Availability | VoID file availability check for CaLiGraph took 0.0005803108215332031s
Extra | Recovery of all triples for CaLiGraph took 1.49037766456604s
Performance | Total latancy measurement for CaLiGraph took 1.0640904903411865s
Amount of data | Number of triples check for CaLiGraph took 12.943404197692871s
Interoperability | New terms check for CaLiGraph took 1.9871056079864502s
Versatility | Languages check for CaLiGraph took 60.28759980201721s
Interpretability | Number of blank nodes check for CaLiGraph took 0.25838732719421387s
Security | Check HTTPS for CaLiGraph took 0.11210489273071289s
Interpretability | RDF structures check for CaLiGraph took 0.4457533359527588s
Versatility | Serialization formats check for CaLiGraph took 0.3103024959564209s
Availability | RDF dump link check for CaLiGraph took 0.24555158615112305s
License | MR license check for CaLiGraph took 0.4172496795654297s
License | HR license check for CaLiGraph took 60.31101965904236s
Amount of data | Number of property check for CaLiGraph took 0.24156951904296875s
Understandability | Number of label check for CaLiGraph took 4.808354616165161s
Understandability | URI regex check for CaLiGraph took 0.5066943168640137s
Understandability | Vocabs check for CaLiGraph took 0.25995373725891113s
Verifiability | Authors check for CaLiGraph took 0.27843737602233887s
Verifiability | Publishers check for CaLiGraph took 0.2472984790802002s
Performance | Throughput check for CaLiGraph took 10.893988847732544s
Amount of data | Check the number of entities for CaLiGraph took 0.01645684242248535s
Verifiability | Contribs. check for CaLiGraph took 0.23613405227661133s
Interlinking | sameAs chians check for CaLiGraph took 0.6950654983520508s
Interlinking | skos check for CaLiGraph took 0.37950730323791504s
Interlinking | skos check for CaLiGraph took 0.20206284523010254s
Timeliness | dataset update frequency check for CaLiGraph took 0.31023406982421875s
Currency | Creation date check for CaLiGraph took 0.5482604503631592s
Currency | Modification date check for CaLiGraph took 0.5192344188690186s
Rep.Conc. | URIs length for CaLiGraph took 60.98569297790527s
Interoperability | New vocabularies check for CaLiGraph took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.24425411224365234s
Accuracy | Check Functional Property for CaLiGraph took 0.2721683979034424s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.272036075592041s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.4905972480773926s
Accuracy | Check White space in annotation for CaLiGraph took 0.026337385177612305s
Accuracy | Check Datatype consistency for CaLiGraph took 0.05175280570983887s
Consistency | Disjoint class check for CaLiGraph took 0.3009343147277832s
Consistency | Check Misplaced properties for CaLiGraph took 60.84296703338623s
Consistency | Misplaced classes for CaLiGraph took 0.4511425495147705s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9906327724456787s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.3674960136413574s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.620052337646484s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.035405874252319336s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.42439937591552734s
Security | Sign check for CaLiGraph took 0.3596944808959961s
Availability | Check URIs Dereferenciability for CaLiGraph took 21.10252571105957s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.33985066413879395s
Reputation | Calculation of the PageRank for CaLiGraph took 0.021413803100585938s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 1.2159347534179688e-05s
INFO | --- Analysis for CaLiGraph took 1579.2706677913666s
Availability | SPARQL endpoint availability check for CaLiGraph took 5.904335975646973s
Availability | VoID file availability check for CaLiGraph took 0.0006604194641113281s
Extra | Recovery of all triples for CaLiGraph took 8.891841173171997s
Performance | Total latancy measurement for CaLiGraph took 1.019057035446167s
Amount of data | Number of triples check for CaLiGraph took 13.011023044586182s
Interoperability | New terms check for CaLiGraph took 1.9485774040222168s
Versatility | Languages check for CaLiGraph took 60.3154034614563s
Interpretability | Number of blank nodes check for CaLiGraph took 0.23800230026245117s
Security | Check HTTPS for CaLiGraph took 0.11316537857055664s
Interpretability | RDF structures check for CaLiGraph took 0.23651504516601562s
Versatility | Serialization formats check for CaLiGraph took 9.141330242156982s
Availability | RDF dump link check for CaLiGraph took 9.277520418167114s
License | MR license check for CaLiGraph took 12.114285230636597s
License | HR license check for CaLiGraph took 81.61162328720093s
Amount of data | Number of property check for CaLiGraph took 10.503353595733643s
Understandability | Number of label check for CaLiGraph took 14.306193351745605s
Understandability | URI regex check for CaLiGraph took 35.31972670555115s
Understandability | Vocabs check for CaLiGraph took 9.89479374885559s
Verifiability | Authors check for CaLiGraph took 10.635864734649658s
Verifiability | Publishers check for CaLiGraph took 11.322024822235107s
Performance | Throughput check for CaLiGraph took 152.345223903656s
Amount of data | Check the number of entities for CaLiGraph took 0.014238119125366211s
Verifiability | Contribs. check for CaLiGraph took 0.24740910530090332s
Interlinking | sameAs chians check for CaLiGraph took 0.6490225791931152s
Interlinking | skos check for CaLiGraph took 0.21883773803710938s
Interlinking | skos check for CaLiGraph took 0.20403766632080078s
Timeliness | dataset update frequency check for CaLiGraph took 0.2268662452697754s
Currency | Creation date check for CaLiGraph took 0.4775688648223877s
Currency | Modification date check for CaLiGraph took 0.46094536781311035s
Rep.Conc. | URIs length for CaLiGraph took 60.981775522232056s
Interoperability | New vocabularies check for CaLiGraph took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2438817024230957s
Accuracy | Check Functional Property for CaLiGraph took 0.21606850624084473s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.24453091621398926s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5543951988220215s
Accuracy | Check White space in annotation for CaLiGraph took 0.026888132095336914s
Accuracy | Check Datatype consistency for CaLiGraph took 0.050382375717163086s
Consistency | Disjoint class check for CaLiGraph took 0.23811817169189453s
Consistency | Check Misplaced properties for CaLiGraph took 60.8790168762207s
Consistency | Misplaced classes for CaLiGraph took 0.4774510860443115s
Consistency | Check Ontology hijacking for CaLiGraph took 2.022130012512207s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.361457109451294s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.620614767074585s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.029674291610717773s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4528083801269531s
Security | Sign check for CaLiGraph took 0.22628068923950195s
Availability | Check URIs Dereferenciability for CaLiGraph took 11.12821340560913s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.36443042755126953s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02211451530456543s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.843971252441406e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 1.1920928955078125e-05s
INFO | --- Analysis for caligraph took 2396.465215921402s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.06118345260620117s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.2901303768157959s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.021219730377197266s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.62396240234375e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.1920928955078125e-05s
INFO | --- Analysis for cap-italy-rdf took 60.42178988456726s
Availability | SPARQL endpoint availability check for person took 9.202957153320312e-05s
Availability | VoID file availability check for person took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for person took 26.383418560028076s
Reputation | Calculation of the PageRank for person took 0.02140522003173828s
Interlinking | Calculation of Degree of Connection for person took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for person took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for person took 3.3855438232421875e-05s
Believability | Calculation of trust value for person took 7.867813110351562e-06s
INFO | --- Analysis for card took 91.1752667427063s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 9.441375732421875e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.34036922454833984s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.02118086814880371s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0011420249938964844s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 6.461143493652344e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.621246337890625e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 171.1657407283783s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.5899813175201416s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0006151199340820312s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 112.93900609016418s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 0.924750566482544s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 9.543380737304688s
Interoperability | New terms check for Norway catch records dataset @PSNC took 14.352518081665039s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.1734571456909s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 2.330970287322998s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.26201915740966797s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 7.291400671005249s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.2823820114135742s
License | MR license check for Norway catch records dataset @PSNC took 0.5400350093841553s
License | HR license check for Norway catch records dataset @PSNC took 300.24254035949707s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.20784664154052734s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.185828924179077s
Understandability | URI regex check for Norway catch records dataset @PSNC took 0.8320069313049316s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.44876933097839355s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.19523239135742188s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.2653481960296631s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.427250385284424s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 9.942054748535156e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.2009897232055664s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.186659574508667s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.538506269454956s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4190962314605713s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 6.840601205825806s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.48360610008239746s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.22774624824523926s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 157.65889286994934s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.21298789978027344s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.3626244068145752s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.3595597743988037s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 33.61146521568298s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.6941094398498535s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.662113666534424s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.20920538902282715s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 86.41806149482727s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.442975521087646s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 34.60931921005249s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.4489109516143799s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 86.79176306724548s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.7871510982513428s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.5860238075256348s
Security | Sign check for Norway catch records dataset @PSNC took 1.3041844367980957s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 10.010795831680298s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 29.035810947418213s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.021762609481811523s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 2.7418136596679688e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.863739013671875e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 8.58306884765625e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2412.271019220352s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.982948303222656e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007405281066894531s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 27.46609902381897s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.022319793701171875s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0010051727294921875s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00013184547424316406s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.2874603271484375e-05s
INFO | --- Analysis for ce4r took 180.70670986175537s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4467024803161621s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005352497100830078s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.28839111328125s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.8390541076660156s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.38145923614501953s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.7368276119232178s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.135393381118774s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1670382022857666s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2971515655517578s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1610393524169922s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15624046325683594s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.27671289443969727s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.23274445533752441s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15488934516906738s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2590789794921875s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.37061452865600586s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14589762687683105s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1930239200592041s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15733671188354492s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.969865083694458s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 0.00011277198791503906s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.34931325912475586s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18659281730651855s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7719247341156006s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17029786109924316s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17389869689941406s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.43012070655822754s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.37888360023498535s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.164033889770508s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16876983642578125s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.25701189041137695s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.31322669982910156s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 1.7956631183624268s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028835773468017578s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.02945113182067871s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3835301399230957s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.2740273475646973s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.946960687637329s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.3737995624542236s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.5954184532165527s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03171181678771973s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.2386643886566162s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.216963529586792s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 3079.1056411266327s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 24.407005548477173s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.0209200382232666s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 5.507469177246094e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.33514404296875e-05s
INFO | --- Analysis for ceo took 3337.3685462474823s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.5299530029296875e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0007455348968505859s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.30150270462036133s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.02202320098876953s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.7670135498046875e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.2874603271484375e-05s
INFO | --- Analysis for chat-game-corpus took 109.0537621974945s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 9.679794311523438e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0009000301361083984s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.38089561462402344s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.021147727966308594s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0008139610290527344s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 6.413459777832031e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.1920928955078125e-05s
INFO | --- Analysis for chem2bio2rdf took 186.3260636329651s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.5656359195709229s
Availability | VoID file availability check for ChEMBL RDF took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.30182576179504395s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.021001577377319336s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 6.0558319091796875e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.2636184692382812e-05s
INFO | --- Analysis for chembl-rdf took 78.52225494384766s
Availability | SPARQL endpoint availability check for chemdb  dataset took 0.8489727973937988s
Availability | VoID file availability check for chemdb  dataset took 0.0005662441253662109s
Extra | Recovery of all triples for chemdb  dataset took 5.285290241241455s
Performance | Total latancy measurement for chemdb  dataset took 2.685105085372925s
Amount of data | Number of triples check for chemdb  dataset took 0.5925381183624268s
Interoperability | New terms check for chemdb  dataset took 3.6947455406188965s
Versatility | Languages check for chemdb  dataset took 22.479742527008057s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5597965717315674s
Interpretability | RDF structures check for chemdb  dataset took 0.5984671115875244s
Versatility | Serialization formats check for chemdb  dataset took 0.5860061645507812s
Availability | RDF dump link check for chemdb  dataset took 0.5327932834625244s
License | MR license check for chemdb  dataset took 0.6026613712310791s
License | HR license check for chemdb  dataset took 3.1032233238220215s
Amount of data | Number of property check for chemdb  dataset took 0.5569183826446533s
Understandability | Number of label check for chemdb  dataset took 0.5742549896240234s
Understandability | URI regex check for chemdb  dataset took 1.1170294284820557s
Understandability | Vocabs check for chemdb  dataset took 0.5212414264678955s
Verifiability | Authors check for chemdb  dataset took 0.5358376502990723s
Verifiability | Publishers check for chemdb  dataset took 0.5357804298400879s
Performance | Throughput check for chemdb  dataset took 10.772810935974121s
Amount of data | Check the number of entities for chemdb  dataset took 7.343292236328125e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.548210859298706s
Interlinking | sameAs chians check for chemdb  dataset took 0.5657942295074463s
Interlinking | skos check for chemdb  dataset took 0.5979855060577393s
Interlinking | skos check for chemdb  dataset took 0.5419507026672363s
Timeliness | dataset update frequency check for chemdb  dataset took 0.5432147979736328s
Currency | Creation date check for chemdb  dataset took 1.0942323207855225s
Currency | Modification date check for chemdb  dataset took 1.090946912765503s
Rep.Conc. | URIs length for chemdb  dataset took 3.1192657947540283s
Interoperability | New vocabularies check for chemdb  dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5610649585723877s
Accuracy | Check Functional Property for chemdb  dataset took 0.5584015846252441s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.5351474285125732s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.324939250946045s
Accuracy | Check White space in annotation for chemdb  dataset took 0.03013300895690918s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.04190182685852051s
Consistency | Disjoint class check for chemdb  dataset took 0.5465590953826904s
Consistency | Check Misplaced properties for chemdb  dataset took 1.2927026748657227s
Consistency | Misplaced classes for chemdb  dataset took 0.6483829021453857s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.699920415878296s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.3687379360198975s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 2.1180002689361572s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.033844709396362305s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5530545711517334s
Security | Sign check for chemdb  dataset took 0.6553668975830078s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2708.379462480545s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.533623456954956s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.021417617797851562s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.939338684082031e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb  dataset took 1.2636184692382812e-05s
INFO | --- Analysis for chemdb-basicInfo took 7419.19667673111s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.0001049041748046875s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0003178119659423828s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 28.95032000541687s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.024559497833251953s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0009765625s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 6.866455078125e-05s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.239776611328125e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 230.27929043769836s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5544309616088867s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0005049705505371094s
Extra | Recovery of all triples for chemdb phase transition dataset took 5.295267105102539s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.6974146366119385s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.588674783706665s
Interoperability | New terms check for chemdb phase transition dataset took 3.6769604682922363s
Versatility | Languages check for chemdb phase transition dataset took 22.673911809921265s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5761818885803223s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5620005130767822s
Versatility | Serialization formats check for chemdb phase transition dataset took 0.5625593662261963s
Availability | RDF dump link check for chemdb phase transition dataset took 0.5198085308074951s
License | MR license check for chemdb phase transition dataset took 0.5322644710540771s
License | HR license check for chemdb phase transition dataset took 3.1236720085144043s
Amount of data | Number of property check for chemdb phase transition dataset took 0.57564377784729s
Understandability | Number of label check for chemdb phase transition dataset took 0.5705127716064453s
Understandability | URI regex check for chemdb phase transition dataset took 1.0560741424560547s
Understandability | Vocabs check for chemdb phase transition dataset took 0.5368621349334717s
Verifiability | Authors check for chemdb phase transition dataset took 0.5291342735290527s
Verifiability | Publishers check for chemdb phase transition dataset took 0.5300388336181641s
Performance | Throughput check for chemdb phase transition dataset took 10.727551937103271s
Amount of data | Check the number of entities for chemdb phase transition dataset took 9.894371032714844e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.5426239967346191s
Interlinking | sameAs chians check for chemdb phase transition dataset took 0.5762588977813721s
Interlinking | skos check for chemdb phase transition dataset took 0.545058012008667s
Interlinking | skos check for chemdb phase transition dataset took 0.5307443141937256s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 0.5281412601470947s
Currency | Creation date check for chemdb phase transition dataset took 1.0940911769866943s
Currency | Modification date check for chemdb phase transition dataset took 1.099334955215454s
Rep.Conc. | URIs length for chemdb phase transition dataset took 3.1213431358337402s
Interoperability | New vocabularies check for chemdb phase transition dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.5582740306854248s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.5524487495422363s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.5347695350646973s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 2.2861242294311523s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.030524492263793945s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.034689903259277344s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.5307941436767578s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.3161895275115967s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6433041095733643s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 3.6498818397521973s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.3711652755737305s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 2.1135807037353516s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.033322811126708984s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.56203293800354s
Security | Sign check for chemdb phase transition dataset took 0.5483973026275635s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2693.5829458236694s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.57395339012146s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.021570920944213867s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 9.5367431640625e-07s
Believability | Calculation of trust value for chemdb phase transition dataset took 8.106231689453125e-06s
INFO | --- Analysis for chemdb-phaseTransition took 7369.46461892128s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.554250955581665s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0005211830139160156s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 5.273128032684326s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.781116008758545s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5778639316558838s
Interoperability | New terms check for chemdb thermochemistry dataset took 3.697446823120117s
Versatility | Languages check for chemdb thermochemistry dataset took 23.04568862915039s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5803232192993164s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5648856163024902s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 0.578937292098999s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.5354914665222168s
License | MR license check for chemdb thermochemistry dataset took 0.5478684902191162s
License | HR license check for chemdb thermochemistry dataset took 3.1723968982696533s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5740041732788086s
Understandability | Number of label check for chemdb thermochemistry dataset took 0.568871021270752s
Understandability | URI regex check for chemdb thermochemistry dataset took 1.0785257816314697s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.5463950634002686s
Verifiability | Authors check for chemdb thermochemistry dataset took 0.5276925563812256s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.5465683937072754s
Performance | Throughput check for chemdb thermochemistry dataset took 11.184578657150269s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 7.295608520507812e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.5386641025543213s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 0.5752568244934082s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5462346076965332s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5275893211364746s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 0.5351932048797607s
Currency | Creation date check for chemdb thermochemistry dataset took 1.1221871376037598s
Currency | Modification date check for chemdb thermochemistry dataset took 1.0963685512542725s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.1599321365356445s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.5356073379516602s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.560753583908081s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.5252511501312256s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 2.3570199012756348s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.0303802490234375s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03541421890258789s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.5291590690612793s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.324172019958496s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6587123870849609s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 3.7058584690093994s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.377683162689209s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 2.1190223693847656s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.033484458923339844s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5762491226196289s
Security | Sign check for chemdb thermochemistry dataset took 0.5285351276397705s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2717.4436435699463s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 26.521949529647827s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.021816492080688477s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 1.2636184692382812e-05s
INFO | --- Analysis for chemdb-thermochemistry took 7382.840667724609s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 9.989738464355469e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.340709924697876s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.02117633819580078s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.409385681152344e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.1682510375976562e-05s
INFO | --- Analysis for chempedia-rdf took 121.05729937553406s
Availability | SPARQL endpoint availability check for Chiman Maru took 9.608268737792969e-05s
Availability | VoID file availability check for Chiman Maru took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.3047983646392822s
Reputation | Calculation of the PageRank for Chiman Maru took 0.022189855575561523s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.695487976074219e-05s
Believability | Calculation of trust value for Chiman Maru took 1.2874603271484375e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 142.59382724761963s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.500928401947s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 23.06562113761902s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.023103713989257812s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0008175373077392578s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 4.6253204345703125e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 7.62939453125e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 1031.242553949356s
Availability | SPARQL endpoint availability check for Chronicling America took 9.965896606445312e-05s
Availability | VoID file availability check for Chronicling America took 0.0009136199951171875s
Completeness | Calculation of interlinking completeness for Chronicling America took 32.20186734199524s
Reputation | Calculation of the PageRank for Chronicling America took 0.021379470825195312s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00011849403381347656s
Believability | Calculation of trust value for Chronicling America took 1.1205673217773438e-05s
INFO | --- Analysis for chronicling-america took 416.91196393966675s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.6493208408355713s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006806850433349609s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 83.10761451721191s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.6237809658050537s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 1.381730318069458s
Interoperability | New terms check for Cultural Heritage Thesaurus took 3.0689537525177s
Versatility | Languages check for Cultural Heritage Thesaurus took 5.282379627227783s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 1.0604534149169922s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.30631256103515625s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.29611635208129883s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 6.269111394882202s
License | MR license check for Cultural Heritage Thesaurus took 0.3346126079559326s
License | HR license check for Cultural Heritage Thesaurus took 0.7020556926727295s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.36636972427368164s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.4816577434539795s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.6449160575866699s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.30886292457580566s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.3156125545501709s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.30724143981933594s
Performance | Throughput check for Cultural Heritage Thesaurus took 12.404376983642578s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 8.606910705566406e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.3534579277038574s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.3117947578430176s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3346128463745117s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.35756778717041016s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.29175639152526855s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6700794696807861s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.6349732875823975s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 27.91487979888916s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 1.6091997623443604s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.3287489414215088s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.3220102787017822s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.29006195068359375s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 7.530150413513184s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.2279984951019287s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.3286857604980469s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.9841508865356445s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.2759113311767578s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 7.630149841308594s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 3.4873831272125244s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.0001595020294189453s
Security | Sign check for Cultural Heritage Thesaurus took 0.3303403854370117s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 448.5263476371765s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 22.929372787475586s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.12925934791564941s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0008215904235839844s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00011777877807617188s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.5387701988220215s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.7404556274414062e-05s
INFO | --- Analysis for cht took 794.1354207992554s
Availability | SPARQL endpoint availability check for ciard-ring took 9.1552734375e-05s
Availability | VoID file availability check for ciard-ring took 0.0014073848724365234s
Completeness | Calculation of interlinking completeness for ciard-ring took 26.170312881469727s
Reputation | Calculation of the PageRank for ciard-ring took 0.020789146423339844s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.863739013671875e-05s
Believability | Calculation of trust value for ciard-ring took 1.239776611328125e-05s
INFO | --- Analysis for ciard-ring took 132.64576745033264s
Availability | SPARQL endpoint availability check for Cine Figure took 9.012222290039062e-05s
Availability | VoID file availability check for Cine Figure took 0.0011649131774902344s
Completeness | Calculation of interlinking completeness for Cine Figure took 22.401292085647583s
Reputation | Calculation of the PageRank for Cine Figure took 0.021173477172851562s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 5.14984130859375e-05s
Believability | Calculation of trust value for Cine Figure took 1.2636184692382812e-05s
INFO | --- Analysis for Cine_Figure took 127.13262462615967s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 1.841299295425415s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0007600784301757812s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.3253917694091797s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.021392107009887695s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.839897155761719e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.0251998901367188e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 108.73857092857361s
Availability | SPARQL endpoint availability check for CIPFA took 9.274482727050781e-05s
Availability | VoID file availability check for CIPFA took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for CIPFA took 29.10020089149475s
Reputation | Calculation of the PageRank for CIPFA took 0.02147841453552246s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for CIPFA took 4.458427429199219e-05s
Believability | Calculation of trust value for CIPFA took 8.58306884765625e-06s
INFO | --- Analysis for cipfa took 225.60309290885925s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.05651807785034s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0007894039154052734s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 22.335432529449463s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.021446943283081055s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00041985511779785156s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.1682510375976562e-05s
INFO | --- Analysis for ckan took 430.29081416130066s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.6071867942810059s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 26.95246171951294s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.021203994750976562s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.9114227294921875e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.2636184692382812e-05s
INFO | --- Analysis for CLaSSES took 163.8929877281189s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.38690185546875e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.000804901123046875s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.3054828643798828s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.0211942195892334s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.3855438232421875e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.1682510375976562e-05s
INFO | --- Analysis for classical_temples took 88.12536597251892s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 0.9651868343353271s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 25.932106494903564s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.0213167667388916s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 0.00010156631469726562s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 9.775161743164062e-06s
INFO | --- Analysis for clean-energy-data-reegle took 135.80959677696228s
Availability | SPARQL endpoint availability check for CLLD-afbo took 9.608268737792969e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 27.097132205963135s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.021677732467651367s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 8.797645568847656e-05s
Believability | Calculation of trust value for CLLD-afbo took 9.298324584960938e-06s
INFO | --- Analysis for clld-afbo took 178.61981987953186s
Availability | SPARQL endpoint availability check for CLLD-APICS took 0.00010204315185546875s
Availability | VoID file availability check for CLLD-APICS took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 22.421383142471313s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.02275371551513672s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 9.274482727050781e-05s
Believability | Calculation of trust value for CLLD-APICS took 7.3909759521484375e-06s
INFO | --- Analysis for clld-apics took 135.2070815563202s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.9591064453125e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.4911031723022461s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 23.37185311317444s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.028498411178588867s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0013730525970458984s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 5.626678466796875e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-EWAVE took 9.5367431640625e-07s
Believability | Calculation of trust value for CLLD-EWAVE took 7.3909759521484375e-06s
INFO | --- Analysis for clld-ewave took 159.29820370674133s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 6.818771362304688e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.5216872692108154s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 20.826973915100098s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.022126197814941406s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 4.4345855712890625e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.0001010894775390625s
Interoperability | Check the re-using of existing vocabs for CLLD-GLOTTOLOG took 7.152557373046875e-07s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.0728836059570312e-05s
INFO | --- Analysis for clld-glottolog took 117.02448415756226s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 9.107589721679688e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0007674694061279297s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 22.799145221710205s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.021437644958496094s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0011510848999023438s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 0.00011277198791503906s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.1205673217773438e-05s
INFO | --- Analysis for clld-phoible took 119.66104340553284s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 9.298324584960938e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.3065922260284424s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.021155834197998047s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 8.988380432128906e-05s
Believability | Calculation of trust value for CLLD-SAILS took 1.239776611328125e-05s
INFO | --- Analysis for clld-sails took 95.02713918685913s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.363059997558594e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0008385181427001953s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.30629658699035645s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.022528648376464844s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 9.72747802734375e-05s
Believability | Calculation of trust value for CLLD-WALS took 1.2159347534179688e-05s
INFO | --- Analysis for clld-wals took 51.027336835861206s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 9.107589721679688e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 26.70237398147583s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.021094560623168945s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 8.416175842285156e-05s
Believability | Calculation of trust value for CLLD-WOLD took 1.1920928955078125e-05s
INFO | --- Analysis for clld-wold took 136.1051549911499s
Availability | SPARQL endpoint availability check for COD inventory took 0.00042700767517089844s
Availability | VoID file availability check for COD inventory took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for COD inventory took 28.210402011871338s
Reputation | Calculation of the PageRank for COD inventory took 0.021229028701782227s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for COD inventory took 4.649162292480469e-05s
Believability | Calculation of trust value for COD inventory took 1.2636184692382812e-05s
INFO | --- Analysis for cod-inventory took 201.44646501541138s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.2961575984954834s
Availability | VoID file availability check for Cooperation Databank took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 22.755625247955322s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.02115488052368164s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 4.553794860839844e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.2874603271484375e-05s
INFO | --- Analysis for CoDa took 148.234308719635s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.9240975379943848s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.28838229179382324s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.023320436477661133s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.504753112792969e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 9.298324584960938e-06s
INFO | --- Analysis for coins-openuplabs took 110.31103992462158s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.730154275894165s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.3016071319580078s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.02142953872680664s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.869171142578125e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 1.3113021850585938e-05s
INFO | --- Analysis for CoLChina_sp2000 took 160.62006616592407s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.08887171745300293s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 26.701125383377075s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.02118825912475586s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 5.435943603515625e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.4781951904296875e-05s
INFO | --- Analysis for colinda took 150.04780626296997s
Availability | SPARQL endpoint availability check for CN  2012 took 26.07975459098816s
Availability | VoID file availability check for CN  2012 took 0.0010645389556884766s
Completeness | Calculation of interlinking completeness for CN  2012 took 27.512559413909912s
Reputation | Calculation of the PageRank for CN  2012 took 0.02173900604248047s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 5.078315734863281e-05s
Believability | Calculation of trust value for CN  2012 took 9.059906005859375e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 309.91777753829956s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.577890157699585s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0004138946533203125s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.3941810131072998s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.021444082260131836s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 4.2438507080078125e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for CompHistSem took 110.53777599334717s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 1.766420841217041s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0008151531219482422s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 24.61196494102478s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02565789222717285s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 4.267692565917969e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.3113021850585938e-05s
INFO | --- Analysis for comsode-d3-2 took 180.72213339805603s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 9.846687316894531e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.00039696693420410156s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 28.6683349609375s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.02126455307006836s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.845329284667969e-05s
Believability | Calculation of trust value for 2011 US Congress People took 9.5367431640625e-06s
INFO | --- Analysis for congresspeople took 158.39491081237793s
Availability | SPARQL endpoint availability check for MIMO took 0.399827241897583s
Availability | VoID file availability check for MIMO took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for MIMO took 0.299999475479126s
Reputation | Calculation of the PageRank for MIMO took 0.021367788314819336s
Interlinking | Calculation of Degree of Connection for MIMO took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.3113021850585938e-05s
Believability | Calculation of trust value for MIMO took 1.2159347534179688e-05s
INFO | --- Analysis for CONNECTED took 112.2360897064209s
Availability | SPARQL endpoint availability check for Copyright Free Music took 5.626678466796875e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.302490234375s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.021535873413085938s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.361701965332031e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.2159347534179688e-05s
INFO | --- Analysis for Copyright_Free_Music took 70.8643262386322s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 5.030632019042969e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 23.63312816619873s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.021175622940063477s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.987022399902344e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.2159347534179688e-05s
INFO | --- Analysis for copyrighttermbank took 157.8885097503662s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.6908857822418213s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.31491613388061523s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.022328615188598633s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 4.1961669921875e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.1444091796875e-05s
INFO | --- Analysis for core took 107.93512201309204s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.6114950180053711s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0005233287811279297s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 119.21458101272583s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.9283151626586914s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 9.347977638244629s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.139344215393066s
Versatility | Languages check for Corine linked dataset @PSNC took 300.23002648353577s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 2.2033066749572754s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.3261897563934326s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 9.152219295501709s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.29420995712280273s
License | MR license check for Corine linked dataset @PSNC took 0.5718884468078613s
License | HR license check for Corine linked dataset @PSNC took 300.22283267974854s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.22914695739746094s
Understandability | Number of label check for Corine linked dataset @PSNC took 1.76621675491333s
Understandability | URI regex check for Corine linked dataset @PSNC took 0.6542654037475586s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.45903992652893066s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.2160625457763672s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.26149725914001465s
Performance | Throughput check for Corine linked dataset @PSNC took 11.322458982467651s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 7.128715515136719e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.18642735481262207s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.21851468086242676s
Interlinking | skos check for Corine linked dataset @PSNC took 0.5145461559295654s
Interlinking | skos check for Corine linked dataset @PSNC took 0.44100332260131836s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 5.216139078140259s
Currency | Creation date check for Corine linked dataset @PSNC took 0.5006616115570068s
Currency | Modification date check for Corine linked dataset @PSNC took 0.2659330368041992s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 153.96736335754395s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.19998550415039062s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.3714559078216553s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.35854649543762207s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 41.31568384170532s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.696643829345703s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.6748082637786865s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.20935916900634766s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 86.94462084770203s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.410168409347534s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 35.91303515434265s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.7044484615325928s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 87.14574670791626s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.789968490600586s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.463787317276001s
Security | Sign check for Corine linked dataset @PSNC took 1.5142755508422852s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 10.186986684799194s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 30.24018883705139s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.021562814712524414s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 4.124641418457031e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 5.9604644775390625e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for Corine_linked_dataset took 2385.116819858551s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 0.00010323524475097656s
Availability | VoID file availability check for Cornetto1.2 took 0.0007455348968505859s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 28.400802850723267s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.021729469299316406s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 6.413459777832031e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.33514404296875e-05s
INFO | --- Analysis for cornetto took 145.68891406059265s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.18833374977111816s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005650520324707031s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 230.87877583503723s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.5762989521026611s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 146.33031940460205s
Versatility | Languages check for Corporate Body Named Authority List  took 300.0789453983307s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 21.30126667022705s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.3432497978210449s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.6831254959106445s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 4.752127647399902s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.22690033912658691s
License | MR license check for Corporate Body Named Authority List  took 0.39121437072753906s
License | HR license check for Corporate Body Named Authority List  took 300.01252031326294s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.21099328994750977s
Understandability | Number of label check for Corporate Body Named Authority List  took 2.313189744949341s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.42786622047424316s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.09790325164794922s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.34957075119018555s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.2942495346069336s
Performance | Throughput check for Corporate Body Named Authority List  took 10.698537826538086s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 7.724761962890625e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.1750025749206543s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 6.507870435714722s
Interlinking | skos check for Corporate Body Named Authority List  took 0.34633779525756836s
Interlinking | skos check for Corporate Body Named Authority List  took 0.4413108825683594s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.4039757251739502s
Currency | Creation date check for Corporate Body Named Authority List  took 0.5115218162536621s
Currency | Modification date check for Corporate Body Named Authority List  took 0.17376160621643066s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 427.46517992019653s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.16308331489562988s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.2098531723022461s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.18108773231506348s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 40.891927003860474s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.0967671871185303s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.7025015354156494s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.18143796920776367s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.4587495326996s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.750697374343872s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 36.94541811943054s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.7070708274841309s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.63111543655396s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.052152395248413s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.5948925018310547s
Security | Sign check for Corporate Body Named Authority List  took 0.33326053619384766s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 11.199283361434937s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 25.03864312171936s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.02104353904724121s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 7.605552673339844e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.430511474609375e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.5735626220703125e-05s
INFO | --- Analysis for corporate-body took 14819.877852201462s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.5757055282592773s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 27.323580980300903s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.022769927978515625s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0011703968048095703s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 5.340576171875e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 8.106231689453125e-06s
INFO | --- Analysis for CorpusFibonacci took 105.00806903839111s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.17914485931396484s
Availability | VoID file availability check for Country Name Authority List took 0.0007016658782958984s
Extra | Recovery of all triples for Country Name Authority List took 163.92916417121887s
Performance | Total latancy measurement for Country Name Authority List took 0.5716586112976074s
Amount of data | Number of triples check for Country Name Authority List took 41.02778434753418s
Interoperability | New terms check for Country Name Authority List took 57.70504331588745s
Versatility | Languages check for Country Name Authority List took 300.1215817928314s
Interpretability | Number of blank nodes check for Country Name Authority List took 16.962130308151245s
Security | Check HTTPS for Country Name Authority List took 0.34047627449035645s
Interpretability | RDF structures check for Country Name Authority List took 0.5801587104797363s
Versatility | Serialization formats check for Country Name Authority List took 4.923881769180298s
Availability | RDF dump link check for Country Name Authority List took 0.24042272567749023s
License | MR license check for Country Name Authority List took 0.42563509941101074s
License | HR license check for Country Name Authority List took 293.43256402015686s
Amount of data | Number of property check for Country Name Authority List took 0.20402979850769043s
Understandability | Number of label check for Country Name Authority List took 3.593036413192749s
Understandability | URI regex check for Country Name Authority List took 0.3705720901489258s
Understandability | Vocabs check for Country Name Authority List took 0.09319496154785156s
Verifiability | Authors check for Country Name Authority List took 0.17313551902770996s
Verifiability | Publishers check for Country Name Authority List took 0.24167609214782715s
Performance | Throughput check for Country Name Authority List took 10.68535590171814s
Amount of data | Check the number of entities for Country Name Authority List took 0.0001125335693359375s
Verifiability | Contribs. check for Country Name Authority List took 0.23002266883850098s
Interlinking | sameAs chians check for Country Name Authority List took 6.932956218719482s
Interlinking | skos check for Country Name Authority List took 0.3344440460205078s
Interlinking | skos check for Country Name Authority List took 0.29506731033325195s
Timeliness | dataset update frequency check for Country Name Authority List took 0.3191967010498047s
Currency | Creation date check for Country Name Authority List took 0.4963252544403076s
Currency | Modification date check for Country Name Authority List took 0.24268817901611328s
Rep.Conc. | URIs length for Country Name Authority List took 404.74519181251526s
Interoperability | New vocabularies check for Country Name Authority List took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.18026208877563477s
Accuracy | Check Functional Property for Country Name Authority List took 0.21756958961486816s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.15244364738464355s
Accuracy | Check Empty annotation labels for Country Name Authority List took 40.550843238830566s
Accuracy | Check White space in annotation for Country Name Authority List took 3.083284378051758s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.6951904296875s
Consistency | Disjoint class check for Country Name Authority List took 0.19708967208862305s
Consistency | Check Misplaced properties for Country Name Authority List took 300.3980073928833s
Consistency | Misplaced classes for Country Name Authority List took 8.692168474197388s
Consistency | Check Ontology hijacking for Country Name Authority List took 38.39455223083496s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.6737089157104492s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.6212537288666s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.069887399673462s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.5407474040985107s
Security | Sign check for Country Name Authority List took 0.42876720428466797s
Availability | Check URIs Dereferenciability for Country Name Authority List took 11.043622970581055s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 17.263026475906372s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.021291255950927734s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 6.4849853515625e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.1920928955078125e-06s
Believability | Calculation of trust value for Country Name Authority List took 1.1444091796875e-05s
INFO | --- Analysis for country-authority-list took 15531.481835365295s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.08117389678955078s
Availability | VoID file availability check for Courts thesaurus took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 26.115781545639038s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.021251440048217773s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 8.130073547363281e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for courts-thesaurus took 215.86347007751465s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 20.545453786849976s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0007779598236083984s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.3545351028442383s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.02133917808532715s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 8.96453857421875e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for Covid-on-the-Web took 158.57216882705688s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.713745594024658s
Availability | VoID file availability check for CPA 2008 took 0.001016855239868164s
Completeness | Calculation of interlinking completeness for CPA 2008 took 28.349356651306152s
Reputation | Calculation of the PageRank for CPA 2008 took 0.021219730377197266s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.5299530029296875e-05s
Believability | Calculation of trust value for CPA 2008 took 3.337860107421875e-05s
INFO | --- Analysis for cpa-2008 took 245.13706707954407s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.4374418258666992s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0006642341613769531s
Extra | Recovery of all triples for Cooperative Patent Classification took 28.611888885498047s
Performance | Total latancy measurement for Cooperative Patent Classification took 0.968580961227417s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.20399808883667s
Versatility | Languages check for Cooperative Patent Classification took 100.27763772010803s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.2751669883728s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.28879833221435547s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.24247074127197266s
Availability | RDF dump link check for Cooperative Patent Classification took 0.2065751552581787s
License | MR license check for Cooperative Patent Classification took 0.20119071006774902s
License | HR license check for Cooperative Patent Classification took 90.31546998023987s
Amount of data | Number of property check for Cooperative Patent Classification took 0.21089792251586914s
Understandability | Number of label check for Cooperative Patent Classification took 90.2308099269867s
Understandability | URI regex check for Cooperative Patent Classification took 0.49418139457702637s
Understandability | Vocabs check for Cooperative Patent Classification took 0.2589287757873535s
Verifiability | Authors check for Cooperative Patent Classification took 0.26931071281433105s
Verifiability | Publishers check for Cooperative Patent Classification took 0.39212656021118164s
Performance | Throughput check for Cooperative Patent Classification took 11.004755020141602s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.987022399902344e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.18054437637329102s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.20117855072021484s
Interlinking | skos check for Cooperative Patent Classification took 0.21465539932250977s
Interlinking | skos check for Cooperative Patent Classification took 0.1792762279510498s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.16156578063964844s
Currency | Creation date check for Cooperative Patent Classification took 0.43635010719299316s
Currency | Modification date check for Cooperative Patent Classification took 0.3540210723876953s
Rep.Conc. | URIs length for Cooperative Patent Classification took 132.4535219669342s
Interoperability | New vocabularies check for Cooperative Patent Classification took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.25798964500427246s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 19.413854837417603s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 3.0182135105133057s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.958131551742554s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.32396435737609863s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 100.41643714904785s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 23.30520987510681s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.7509572505950928s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 101.82717370986938s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.9065446853637695s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.37370967864990234s
Security | Sign check for Cooperative Patent Classification took 0.2227635383605957s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.6565577983856201s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.7379107475280762s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.023326635360717773s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 4.00543212890625e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0013332366943359375s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 6.723403930664062e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 3.337860107421875e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.1205673217773438e-05s
INFO | --- Analysis for CPC took 1274.618447303772s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.3249990940094s
Availability | VoID file availability check for CPC 2008 took 0.000926971435546875s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.5351600646972656s
Reputation | Calculation of the PageRank for CPC 2008 took 0.027217864990234375s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.744529724121094e-05s
Believability | Calculation of trust value for CPC 2008 took 9.059906005859375e-06s
INFO | --- Analysis for cpc-2008 took 294.3025391101837s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.804900407791138s
Availability | VoID file availability check for CPV  2003 took 0.0008740425109863281s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.3452279567718506s
Reputation | Calculation of the PageRank for CPV  2003 took 0.021932363510131836s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.9114227294921875e-05s
Believability | Calculation of trust value for CPV  2003 took 1.0013580322265625e-05s
INFO | --- Analysis for cpv-2003 took 259.73859453201294s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.832078218460083s
Availability | VoID file availability check for CPV 2008 took 0.0009222030639648438s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.30258941650390625s
Reputation | Calculation of the PageRank for CPV 2008 took 0.021236181259155273s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 5.793571472167969e-05s
Believability | Calculation of trust value for CPV 2008 took 9.298324584960938e-06s
INFO | --- Analysis for cpv-2008 took 230.630628824234s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.3453195095062s
Availability | VoID file availability check for crowdsourcing-fb took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.3002474308013916s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.02152276039123535s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 5.030632019042969e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.2636184692382812e-05s
INFO | --- Analysis for crowdsourcing-fb took 645.9341208934784s
Availability | SPARQL endpoint availability check for CRTM took 0.00021028518676757812s
Availability | VoID file availability check for CRTM took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for CRTM took 25.693984985351562s
Reputation | Calculation of the PageRank for CRTM took 0.021474123001098633s
Interlinking | Calculation of Degree of Connection for CRTM took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for CRTM took 4.2438507080078125e-05s
Believability | Calculation of trust value for CRTM took 7.62939453125e-06s
INFO | --- Analysis for crtm took 164.5675754547119s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.641878128051758s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0007300376892089844s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 31.342588663101196s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020986557006835938s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 5.888938903808594e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 9.5367431640625e-06s
INFO | --- Analysis for ctic-public-dataset took 196.05488443374634s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.5093767642974854s
Availability | VoID file availability check for CulturaLinkedData took 0.0006527900695800781s
Extra | Recovery of all triples for CulturaLinkedData took 158.86611032485962s
Performance | Total latancy measurement for CulturaLinkedData took 2.9010891914367676s
Amount of data | Number of triples check for CulturaLinkedData took 0.7380256652832031s
Interoperability | New terms check for CulturaLinkedData took 2.396085739135742s
Versatility | Languages check for CulturaLinkedData took 62.301554441452026s
Interpretability | Number of blank nodes check for CulturaLinkedData took 2.0708446502685547s
Interpretability | RDF structures check for CulturaLinkedData took 2.249816656112671s
Versatility | Serialization formats check for CulturaLinkedData took 0.4644205570220947s
Availability | RDF dump link check for CulturaLinkedData took 0.24760723114013672s
License | MR license check for CulturaLinkedData took 2.3853306770324707s
License | HR license check for CulturaLinkedData took 60.42663526535034s
Amount of data | Number of property check for CulturaLinkedData took 0.25272536277770996s
Understandability | Number of label check for CulturaLinkedData took 1.1169946193695068s
Understandability | URI regex check for CulturaLinkedData took 2.4212806224823s
Understandability | Vocabs check for CulturaLinkedData took 0.289961576461792s
Verifiability | Authors check for CulturaLinkedData took 0.3187236785888672s
Verifiability | Publishers check for CulturaLinkedData took 0.2674551010131836s
Performance | Throughput check for CulturaLinkedData took 21.68292498588562s
Amount of data | Check the number of entities for CulturaLinkedData took 7.414817810058594e-05s
Verifiability | Contribs. check for CulturaLinkedData took 2.08139967918396s
Interlinking | sameAs chians check for CulturaLinkedData took 0.34518003463745117s
Interlinking | skos check for CulturaLinkedData took 0.47524452209472656s
Interlinking | skos check for CulturaLinkedData took 0.21876883506774902s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.2951376438140869s
Currency | Creation date check for CulturaLinkedData took 0.4911632537841797s
Currency | Modification date check for CulturaLinkedData took 2.254359245300293s
Rep.Conc. | URIs length for CulturaLinkedData took 61.41344857215881s
Interoperability | New vocabularies check for CulturaLinkedData took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 2.015813112258911s
Accuracy | Check Functional Property for CulturaLinkedData took 0.2094717025756836s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.2012648582458496s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 40.40522575378418s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6183035373687744s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.3223118782043457s
Consistency | Disjoint class check for CulturaLinkedData took 0.23729705810546875s
Consistency | Check Misplaced properties for CulturaLinkedData took 10.27708911895752s
Consistency | Misplaced classes for CulturaLinkedData took 6.1288909912109375s
Consistency | Check Ontology hijacking for CulturaLinkedData took 44.755019187927246s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.4083595275878906s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 10.038082361221313s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.4133384227752686s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.20470952987670898s
Security | Sign check for CulturaLinkedData took 0.8767256736755371s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 11.617266416549683s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 24.68271803855896s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.02172994613647461s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 4.696846008300781e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 1.9073486328125e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.3113021850585938e-05s
INFO | --- Analysis for culturalinkeddata took 725.0616164207458s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2741570472717285s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2869877815246582s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.021182775497436523s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.506111145019531e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 1.0251998901367188e-05s
INFO | --- Analysis for cz-ares-or took 103.14137029647827s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11167716979980469s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0008111000061035156s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 27.763089656829834s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.02104806900024414s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.673004150390625e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 9.298324584960938e-06s
INFO | --- Analysis for cz-ares-rzp took 138.04477524757385s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.10015368461608887s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.2828340530395508s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.02285027503967285s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0008153915405273438s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 5.173683166503906e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 5.7220458984375e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 157.28428983688354s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.10706400871276855s
Availability | VoID file availability check for Integrated pollution registry took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.32586097717285156s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.021140575408935547s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 4.7206878662109375e-05s
Believability | Calculation of trust value for Integrated pollution registry took 9.5367431640625e-06s
INFO | --- Analysis for cz-cenia-pollution took 108.15852737426758s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.10680365562438965s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.29722142219543457s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02122187614440918s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 4.2438507080078125e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 1.0013580322265625e-05s
INFO | --- Analysis for cz-contracts took 112.40584063529968s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.1393601894378662s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.3500657081604004s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.021018028259277344s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 4.649162292480469e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 9.5367431640625e-06s
INFO | --- Analysis for cz-ctia-bans took 121.54353308677673s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.11582708358764648s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0008742809295654297s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 28.162083625793457s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.021367311477661133s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 4.7206878662109375e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 9.059906005859375e-06s
INFO | --- Analysis for cz-ctia-confiscations took 215.42755937576294s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11727499961853027s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.410245418548584s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.021793603897094727s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.814697265625e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 6.4373016357421875e-06s
INFO | --- Analysis for cz-ctia-focus took 106.83745694160461s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.1155250072479248s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0009419918060302734s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 30.331666946411133s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.022334575653076172s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0015881061553955078s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 7.748603820800781e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 8.821487426757812e-06s
INFO | --- Analysis for cz-ctia-inspections took 165.21158361434937s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.11232614517211914s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.3044910430908203s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.023108243942260742s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0012390613555908203s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 5.316734313964844e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
INFO | --- Analysis for cz-ctia-sanctions took 165.55341815948486s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.19534921646118164s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.36785125732421875s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.022806406021118164s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.8160552978515625e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 9.059906005859375e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 154.63997769355774s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.12086248397827148s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.3530888557434082s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.021270036697387695s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.790855407714844e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 9.775161743164062e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 164.81144881248474s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.6025519371032715s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0004131793975830078s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.2992391586303711s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.021661758422851562s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.482269287109375e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-czso-average-salaries took 55.07062816619873s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.3456580638885498s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 26.081296920776367s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.02099895477294922s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.482269287109375e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 58.934486389160156s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.34081172943115234s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 29.821325063705444s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.021095752716064453s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.245208740234375e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 9.5367431640625e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 136.14819955825806s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.3629889488220215s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.2994372844696045s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.021474838256835938s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.839897155761719e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-czso-job-applicants took 136.96924352645874s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.36666011810302734s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.32794737815856934s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.021105051040649414s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.5299530029296875e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 166.02982091903687s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.330873966217041s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0008521080017089844s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.350736141204834s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.02136993408203125s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 4.649162292480469e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-regions took 134.94472432136536s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3393990993499756s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 29.40601086616516s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.02130270004272461s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0008828639984130859s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.9114227294921875e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 141.86238598823547s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.35609889030456543s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.35500001907348633s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.02106928825378418s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.3392181396484375e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-czso-social-service-facilities took 54.14383244514465s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.38807201385498047s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2886214256286621s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.021271944046020508s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 4.8160552978515625e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 138.68695497512817s
Availability | SPARQL endpoint availability check for ATC groups took 0.11256527900695801s
Availability | VoID file availability check for ATC groups took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for ATC groups took 0.4293556213378906s
Reputation | Calculation of the PageRank for ATC groups took 0.021342039108276367s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for ATC groups took 8.058547973632812e-05s
Believability | Calculation of trust value for ATC groups took 1.1444091796875e-05s
INFO | --- Analysis for cz-eh-1-atc took 165.4472794532776s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.11341166496276855s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.3025810718536377s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.021309852600097656s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 4.291534423828125e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 9.298324584960938e-06s
INFO | --- Analysis for cz-fulfillments took 141.12283277511597s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.043381690979003906s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 24.537794828414917s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.0227508544921875s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0010180473327636719s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 5.745887756347656e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 9.298324584960938e-06s
INFO | --- Analysis for cz-ic took 158.21742367744446s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.13444185256958008s
Availability | VoID file availability check for List of Czech data boxes took 0.0006914138793945312s
Extra | Recovery of all triples for List of Czech data boxes took 154.91323971748352s
Performance | Total latancy measurement for List of Czech data boxes took 0.6367924213409424s
Amount of data | Number of triples check for List of Czech data boxes took 56.7962486743927s
Interoperability | New terms check for List of Czech data boxes took 11.56040644645691s
Versatility | Languages check for List of Czech data boxes took 300.15266466140747s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.4039318561553955s
Interpretability | RDF structures check for List of Czech data boxes took 0.14692306518554688s
Versatility | Serialization formats check for List of Czech data boxes took 0.17769765853881836s
Availability | RDF dump link check for List of Czech data boxes took 15.44223427772522s
License | MR license check for List of Czech data boxes took 0.4808650016784668s
License | HR license check for List of Czech data boxes took 59.50263857841492s
Amount of data | Number of property check for List of Czech data boxes took 0.11785268783569336s
Understandability | Number of label check for List of Czech data boxes took 1.1762549877166748s
Understandability | URI regex check for List of Czech data boxes took 0.4799163341522217s
Understandability | Vocabs check for List of Czech data boxes took 0.12980365753173828s
Verifiability | Authors check for List of Czech data boxes took 0.13362789154052734s
Verifiability | Publishers check for List of Czech data boxes took 0.12612032890319824s
Performance | Throughput check for List of Czech data boxes took 10.720058679580688s
Amount of data | Check the number of entities for List of Czech data boxes took 3.2563893795013428s
Verifiability | Contribs. check for List of Czech data boxes took 0.15784096717834473s
Interlinking | sameAs chians check for List of Czech data boxes took 0.5271117687225342s
Interlinking | skos check for List of Czech data boxes took 0.2075207233428955s
Interlinking | skos check for List of Czech data boxes took 0.1080176830291748s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.27141737937927246s
Currency | Creation date check for List of Czech data boxes took 0.2477715015411377s
Currency | Modification date check for List of Czech data boxes took 0.1255054473876953s
Rep.Conc. | URIs length for List of Czech data boxes took 119.53750586509705s
Interoperability | New vocabularies check for List of Czech data boxes took 10.241510152816772s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.4122896194458008s
Accuracy | Check Functional Property for List of Czech data boxes took 0.2639768123626709s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.28756093978881836s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 33.50353932380676s
Accuracy | Check White space in annotation for List of Czech data boxes took 2.811802864074707s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.6806118488311768s
Consistency | Disjoint class check for List of Czech data boxes took 0.12678289413452148s
Consistency | Check Misplaced properties for List of Czech data boxes took 74.18211722373962s
Consistency | Misplaced classes for List of Czech data boxes took 8.395339250564575s
Consistency | Check Ontology hijacking for List of Czech data boxes took 34.59166598320007s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.553637981414795s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 67.66005277633667s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.917222023010254s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.3852870464324951s
Security | Sign check for List of Czech data boxes took 0.19223356246948242s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 404.84123277664185s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 26.371503114700317s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.022950172424316406s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 6.413459777832031e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 10.509304761886597s
Believability | Calculation of trust value for List of Czech data boxes took 1.0013580322265625e-05s
INFO | --- Analysis for cz-list-of-databoxes took 2036.3221549987793s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12399816513061523s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.27849268913269043s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 156.31000351905823s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5794849395751953s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 56.18306565284729s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 11.800637245178223s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.1729338169098s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3011746406555176s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11881899833679199s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.19421887397766113s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 14.964828491210938s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6392576694488525s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 57.53041934967041s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12432980537414551s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.8170773983001709s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.21914124488830566s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11530518531799316s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12357163429260254s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11491966247558594s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.740564823150635s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.3751697540283203s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.143540620803833s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4598240852355957s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.25327253341674805s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10509562492370605s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2773623466491699s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.22082114219665527s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1405329704284668s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 119.94239115715027s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.770719289779663s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3919718265533447s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11660313606262207s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12651300430297852s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 33.9813551902771s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.815688133239746s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.758124351501465s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11839461326599121s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 73.68499159812927s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 8.59623098373413s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 33.7379424571991s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.6243658065795898s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 67.64873623847961s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0010666847229004s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.38720083236694336s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.18726730346679688s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 382.89541935920715s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5943622589111328s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.021818161010742188s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.054473876953125e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 11.739020109176636s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.049041748046875e-05s
INFO | --- Analysis for cz-nace took 2079.3132112026215s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3114476203918457s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0006906986236572266s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.1 took 421.5152053833008s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.8600223064422607s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4165992736816406s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.3658487796783447s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.1 took 219.24090123176575s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.905634641647339s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.4693384170532227s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.1 took 6.90865159034729s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4899132251739502s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.7641723155975342s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.307912588119507s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.19325876235961914s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.471827507019043s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.858802318572998s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4013950824737549s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.8027253150939941s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.5854752063751221s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.1 took 10.508812665939331s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.1 took 7.271766662597656e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.26137351989746094s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.23498082160949707s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.561530590057373s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.1788501739501953s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.6311638355255127s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.670177698135376s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.48903417587280273s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.1 took 88.79187774658203s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.15535974502563477s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3636913299560547s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3891878128051758s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.1 took 75.41427302360535s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.4773027896881104s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.7791876792907715s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.30487632751464844s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.8674259185791016s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.317099571228027s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.1 took 74.47159814834595s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.904176950454712s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.113570690155029s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.2225356101989746s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2580757141113281s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.41977810859680176s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.1 took 991.0917451381683s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.7711565494537354s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.03316068649291992s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.00010132789611816406s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.430511474609375e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.0251998901367188e-05s
INFO | --- Analysis for cz-nkod took 25306.031399011612s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.23233318328857422s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0007574558258056641s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 23.864656686782837s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.022715091705322266s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 4.5299530029296875e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 9.775161743164062e-06s
INFO | --- Analysis for cz-orders took 131.9552927017212s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.20195388793945312s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.26365208625793457s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 165.16202425956726s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.6449887752532959s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 58.883920669555664s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 12.214269399642944s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.1513719558716s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.3426215648651123s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.13489151000976562s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.15958714485168457s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 14.73144817352295s
License | MR license check for Institutions of public power of the Czech Republic took 0.44238996505737305s
License | HR license check for Institutions of public power of the Czech Republic took 61.6183660030365s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.12605953216552734s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.2075507640838623s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.4755432605743408s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.11511492729187012s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.13090133666992188s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.11226654052734375s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.71483564376831s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.3594675064086914s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.12433576583862305s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.4784870147705078s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.2313687801361084s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.12000226974487305s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.29615235328674316s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.2373509407043457s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.11641716957092285s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 127.8687436580658s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 11.611906051635742s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.3730008602142334s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.1739797592163086s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.1591658592224121s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 34.17663526535034s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 2.8062446117401123s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.667180061340332s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.12030220031738281s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 78.0257134437561s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 8.391278982162476s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 35.37033486366272s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.5508918762207031s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 72.15975332260132s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.9179837703704834s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.4073472023010254s
Security | Sign check for Institutions of public power of the Czech Republic took 0.16311883926391602s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 382.6464397907257s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.5750181674957275s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.021626949310302734s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 6.103515625e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 36.64711284637451s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ovm took 2089.275719165802s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.11651492118835449s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.2798933982849121s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.02174687385559082s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 4.267692565917969e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-ovm-agendas took 53.01486563682556s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1158905029296875s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0006124973297119141s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 42.5860641002655s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.5732128620147705s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 16.35208773612976s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 18.134989738464355s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.1859610080719s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.19395112991333008s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.5262060165405273s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.16232657432556152s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.8068492412567139s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12161636352539062s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11503267288208008s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11899089813232422s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6750996112823486s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.226637601852417s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12782621383666992s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.22275519371032715s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12071561813354492s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.64162802696228s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.367134094238281e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1265714168548584s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12105250358581543s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12164807319641113s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11704397201538086s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11788511276245117s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.23415279388427734s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12103629112243652s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 125.6319887638092s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12321710586547852s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.14743328094482422s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12773704528808594s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 11.141661405563354s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.232316493988037s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.666175127029419s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13126659393310547s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 89.23605513572693s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.527745723724365s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 15.979832887649536s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.42476487159729s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 91.09905815124512s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.934377670288086s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.30089521408081055s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1266937255859375s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 943.6295144557953s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.820476770401001s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0214078426361084s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.00014853477478027344s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.384185791015625e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-ruian took 1894.0548658370972s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7147493362426758s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.3131430149078369s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.023612022399902344s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 8.153915405273438e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 1.049041748046875e-05s
INFO | --- Analysis for cz-sao-audited-subjects took 112.62457799911499s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.4927947521209717s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.2916102409362793s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.021077632904052734s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.981590270996094e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 1.1205673217773438e-05s
INFO | --- Analysis for cz-sao-check-actions took 83.0553047657013s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.45381903648376465s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.3213474750518799s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.021084070205688477s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.2901763916015625e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 5.245208740234375e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 31.548194885253906s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.1109311580657959s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.30664515495300293s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.021877527236938477s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 4.506111145019531e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.33514404296875e-05s
INFO | --- Analysis for cz-sidc-drug-ingredients took 102.27592897415161s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.10353922843933105s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 26.99341630935669s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.02445363998413086s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0008487701416015625s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 4.9591064453125e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-sidc-drug-prices took 104.64876437187195s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.11664819717407227s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.3046557903289795s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.02141261100769043s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 4.2438507080078125e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.3113021850585938e-05s
INFO | --- Analysis for cz-sidc-drugs took 77.68519377708435s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.1900925636291504s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0006086826324462891s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 163.6217122077942s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5947327613830566s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 58.75194001197815s
Interoperability | New terms check for Summary types of Czech institutions of public power took 12.034150838851929s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.0726127624512s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.388584852218628s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.12910246849060059s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.1777350902557373s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 14.95618987083435s
License | MR license check for Summary types of Czech institutions of public power took 0.38112449645996094s
License | HR license check for Summary types of Czech institutions of public power took 60.26513934135437s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.11880040168762207s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.251662254333496s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.4532148838043213s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.11259341239929199s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.13676953315734863s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.13709807395935059s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.596744537353516s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.3810408115386963s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.14837336540222168s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.6927089691162109s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.24542808532714844s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.10857439041137695s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.3398265838623047s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.25309038162231445s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.11811113357543945s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 124.75548195838928s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 11.903477430343628s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.3639688491821289s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.22619104385375977s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.23325300216674805s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 33.899710178375244s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 2.8277947902679443s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.6885273456573486s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.10824704170227051s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 77.00776863098145s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 8.442839860916138s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 35.29096579551697s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.415975570678711s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 71.4100661277771s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.9847443103790283s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.3710665702819824s
Security | Sign check for Summary types of Czech institutions of public power took 0.17518377304077148s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 398.54819560050964s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 24.026000022888184s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.021659135818481445s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.76837158203125e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 15.538842916488647s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 9.059906005859375e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2089.622549057007s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.11584687232971191s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0009038448333740234s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.2888956069946289s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.021335124969482422s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 4.00543212890625e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 9.298324584960938e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 73.75716543197632s
Availability | SPARQL endpoint availability check for State funding providers took 0.11107730865478516s
Availability | VoID file availability check for State funding providers took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for State funding providers took 0.2773561477661133s
Reputation | Calculation of the PageRank for State funding providers took 0.021335124969482422s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.601478576660156e-05s
Believability | Calculation of trust value for State funding providers took 9.5367431640625e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 95.58469700813293s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.11347198486328125s
Availability | VoID file availability check for Organizations active in R&D took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.3204672336578369s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.02183675765991211s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0009641647338867188s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 5.2928924560546875e-05s
Believability | Calculation of trust value for Organizations active in R&D took 6.198883056640625e-06s
INFO | --- Analysis for cz-vavai-organizations took 100.10723662376404s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.11353564262390137s
Availability | VoID file availability check for R&D Programmes took 0.0008637905120849609s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.30327367782592773s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020986318588256836s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.363059997558594e-05s
Believability | Calculation of trust value for R&D Programmes took 1.0013580322265625e-05s
INFO | --- Analysis for cz-vavai-programmes took 83.38149762153625s
Availability | SPARQL endpoint availability check for R&D Projects took 0.14456605911254883s
Availability | VoID file availability check for R&D Projects took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for R&D Projects took 21.052144765853882s
Reputation | Calculation of the PageRank for R&D Projects took 0.020919322967529297s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 5.125999450683594e-05s
Believability | Calculation of trust value for R&D Projects took 9.5367431640625e-06s
INFO | --- Analysis for cz-vavai-projects took 116.3409914970398s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.11632490158081055s
Availability | VoID file availability check for Institutional research plans took 0.0008893013000488281s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.3071620464324951s
Reputation | Calculation of the PageRank for Institutional research plans took 0.021271705627441406s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.553794860839844e-05s
Believability | Calculation of trust value for Institutional research plans took 8.344650268554688e-06s
INFO | --- Analysis for cz-vavai-research-plans took 52.05718779563904s
Availability | SPARQL endpoint availability check for Results of R&D took 0.10781598091125488s
Availability | VoID file availability check for Results of R&D took 0.0008459091186523438s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.28760361671447754s
Reputation | Calculation of the PageRank for Results of R&D took 0.021363496780395508s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.3392181396484375e-05s
Believability | Calculation of trust value for Results of R&D took 1.049041748046875e-05s
INFO | --- Analysis for cz-vavai-results took 119.81882119178772s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.11255478858947754s
Availability | VoID file availability check for Tenders in R&D took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.2779974937438965s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.022729158401489258s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.553794860839844e-05s
Believability | Calculation of trust value for Tenders in R&D took 9.298324584960938e-06s
INFO | --- Analysis for cz-vavai-tenders took 79.38499116897583s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.553794860839844e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.3196403980255127s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.02118515968322754s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 4.0531158447265625e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.239776611328125e-05s
INFO | --- Analysis for czech_addresses took 127.11668109893799s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.5912728309631348s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0004024505615234375s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.33243441581726074s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.021776437759399414s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 4.839897155761719e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 8.821487426757812e-06s
INFO | --- Analysis for DanteLatinLoanwords took 147.72469973564148s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.44310927391052246s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.000614166259765625s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 129.43992400169373s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0503976345062256s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 4.278114080429077s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.3129143714904785s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.29622292518616s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.26873016357421875s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.13770842552185059s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 1.1700515747070312s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.2667350769042969s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.2545318603515625s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.2675304412841797s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.32605862617493s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.2315962314605713s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 2.629723072052002s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.4988219738006592s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.24048185348510742s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.3352687358856201s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.23743343353271484s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.54050326347351s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.724761962890625e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.2770264148712158s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 2.161634922027588s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.7012946605682373s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.4269294738769531s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.2593395709991455s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 4.918299198150635s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 1.9185502529144287s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 83.08748531341553s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.2535419464111328s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.32932543754577637s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.29755473136901855s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 49.199769020080566s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.258746862411499s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.6783480644226074s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.6478402614593506s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 21.56052017211914s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.80726408958435s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 44.79596209526062s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.5208039283752441s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 22.881967544555664s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.8616654872894287s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.26274824142456055s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.25406503677368164s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 10.07187008857727s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.6192927360534668s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.022025108337402344s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.0001537799835205078s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 2.1457672119140625e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.3589859008789062e-05s
INFO | --- Analysis for data-bnf-fr took 1010.3412952423096s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.3447408676147461s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 27.927063703536987s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.021283864974975586s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 7.867813110351562e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 5.245208740234375e-06s
INFO | --- Analysis for data-cnr-it took 79.02450919151306s
Availability | SPARQL endpoint availability check for Data.gov took 1.1506526470184326s
Availability | VoID file availability check for Data.gov took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for Data.gov took 0.31371164321899414s
Reputation | Calculation of the PageRank for Data.gov took 0.022795438766479492s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Data.gov took 4.267692565917969e-05s
Believability | Calculation of trust value for Data.gov took 9.775161743164062e-06s
INFO | --- Analysis for data-gov took 98.26919531822205s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.050858259201049805s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.3466224670410156s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.021577835083007812s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.581710815429688e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 9.5367431640625e-06s
INFO | --- Analysis for data-gov-ie took 101.79520106315613s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.363059997558594e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.3055305480957031s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.02118539810180664s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.414817810058594e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 1.3828277587890625e-05s
INFO | --- Analysis for data-gov-uk-time-intervals took 114.0206949710846s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 22.13116955757141s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0007982254028320312s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 22.707664966583252s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02262592315673828s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.413459777832031e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 1.3589859008789062e-05s
INFO | --- Analysis for data-hnm-hu took 318.4467873573303s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.13603496551513672s
Availability | VoID file availability check for Climb Dataincubator took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.2888777256011963s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.02206707000732422s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0009272098541259766s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 9.1552734375e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.0967254638671875e-05s
INFO | --- Analysis for data-incubator-climb took 134.9962248802185s
Availability | SPARQL endpoint availability check for Discogs in RDF took 9.274482727050781e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0007472038269042969s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.2912883758544922s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.021317243576049805s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.72747802734375e-05s
Believability | Calculation of trust value for Discogs in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for data-incubator-discogs took 59.03580355644226s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.061603546142578125s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 31.098825216293335s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.021051883697509766s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.9604644775390625e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 9.298324584960938e-06s
INFO | --- Analysis for data-incubator-metoffice took 115.79852366447449s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.06173276901245117s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0007483959197998047s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 25.84851312637329s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.021268367767333984s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 0.00010561943054199219s
Believability | Calculation of trust value for Moseley Folk Festival Data took 1.2159347534179688e-05s
INFO | --- Analysis for data-incubator-moseley took 235.39343333244324s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.06088829040527344s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 27.710140466690063s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.02127814292907715s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 9.012222290039062e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.6927719116210938e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 132.17382383346558s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 3.6345293521881104s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0007734298706054688s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 27.68311595916748s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.021120548248291016s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 9.107589721679688e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 9.298324584960938e-06s
INFO | --- Analysis for data-incubator-nasa took 94.66086435317993s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.060686349868774414s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.3763132095336914s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.022907733917236328s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.891654968261719e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 7.62939453125e-06s
INFO | --- Analysis for data-incubator-our-airports took 100.18404841423035s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.10781168937683105s
Availability | VoID file availability check for Pokedex data in RDF took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 25.959696769714355s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.02123284339904785s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 0.00010013580322265625s
Believability | Calculation of trust value for Pokedex data in RDF took 1.1682510375976562e-05s
INFO | --- Analysis for data-incubator-pokedex took 55.28355431556702s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.06142473220825195s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.26951169967651367s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020963191986083984s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 9.34600830078125e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.2159347534179688e-05s
INFO | --- Analysis for data-incubator-smcjournals took 55.151347160339355s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.33719849586486816s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006532669067382812s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 30.403136491775513s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 0.6395797729492188s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 16.292312622070312s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.4877586364746094s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.162142276763916s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.146488189697266s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.29076480865478516s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.20672106742858887s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.24421405792236328s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.13121795654296875s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.265244722366333s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.152639627456665s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 2.789552688598633s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 30.1550133228302s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 1.2432527542114258s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.9817812442779541s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.8625876903533936s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.34348416328430176s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 12.727985143661499s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 7.081031799316406e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.18834209442138672s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.7619411945343018s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.19788408279418945s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.1959977149963379s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.29070067405700684s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.46242666244506836s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.6118297576904297s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 41.727272510528564s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 242.3109269142151s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.16548371315002441s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.13726210594177246s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.10845828056335449s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 10.974201440811157s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 2.994586229324341s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.239617824554443s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.1789383888244629s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.4780843257904053s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 8.062767267227173s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 8.721341848373413s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.4964618682861328s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.6782641410827637s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.884708881378174s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.39202308654785156s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.12240147590637207s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.13657641410827637s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 32.60589647293091s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.02123856544494629s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 9.059906005859375e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 271.6144232749939s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 7.62939453125e-06s
INFO | --- Analysis for data-open-ac-uk took 1168.2694237232208s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.7869124412536621s
Availability | VoID file availability check for Persée in RDF took 0.0007145404815673828s
Extra | Recovery of all triples for Persée in RDF took 1.823261022567749s
Performance | Total latancy measurement for Persée in RDF took 0.6704483032226562s
Amount of data | Number of triples check for Persée in RDF took 0.7777464389801025s
Interoperability | New terms check for Persée in RDF took 2.050006628036499s
Versatility | Languages check for Persée in RDF took 120.32321166992188s
Interpretability | Number of blank nodes check for Persée in RDF took 0.4197063446044922s
Interpretability | RDF structures check for Persée in RDF took 0.8507864475250244s
Versatility | Serialization formats check for Persée in RDF took 0.9924075603485107s
Availability | RDF dump link check for Persée in RDF took 0.3213057518005371s
License | MR license check for Persée in RDF took 1.5675947666168213s
License | HR license check for Persée in RDF took 39.11130738258362s
Amount of data | Number of property check for Persée in RDF took 0.13593506813049316s
Understandability | Number of label check for Persée in RDF took 1.8936777114868164s
Understandability | URI regex check for Persée in RDF took 0.8601951599121094s
Understandability | Vocabs check for Persée in RDF took 0.4373345375061035s
Verifiability | Authors check for Persée in RDF took 0.1609508991241455s
Verifiability | Publishers check for Persée in RDF took 0.1212611198425293s
Performance | Throughput check for Persée in RDF took 10.690365314483643s
Amount of data | Check the number of entities for Persée in RDF took 8.606910705566406e-05s
Verifiability | Contribs. check for Persée in RDF took 0.13389039039611816s
Interlinking | sameAs chians check for Persée in RDF took 0.20725154876708984s
Interlinking | skos check for Persée in RDF took 0.7411839962005615s
Interlinking | skos check for Persée in RDF took 0.13552570343017578s
Timeliness | dataset update frequency check for Persée in RDF took 0.6800577640533447s
Currency | Creation date check for Persée in RDF took 0.5570716857910156s
Currency | Modification date check for Persée in RDF took 0.25933146476745605s
Rep.Conc. | URIs length for Persée in RDF took 3.63424015045166s
Interoperability | New vocabularies check for Persée in RDF took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.1499004364013672s
Accuracy | Check Functional Property for Persée in RDF took 0.15130066871643066s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.15834522247314453s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.6556386947631836s
Accuracy | Check White space in annotation for Persée in RDF took 0.038826942443847656s
Accuracy | Check Datatype consistency for Persée in RDF took 0.02956843376159668s
Consistency | Disjoint class check for Persée in RDF took 0.29425978660583496s
Consistency | Check Misplaced properties for Persée in RDF took 2.652271270751953s
Consistency | Misplaced classes for Persée in RDF took 0.21809649467468262s
Consistency | Check Ontology hijacking for Persée in RDF took 1.979886531829834s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.5117523670196533s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 4.03159761428833s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.034811973571777344s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.14986419677734375s
Security | Sign check for Persée in RDF took 0.869459867477417s
Availability | Check URIs Dereferenciability for Persée in RDF took 1404.533349275589s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.5462436676025391s
Reputation | Calculation of the PageRank for Persée in RDF took 0.021529436111450195s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.000118255615234375s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.1920928955078125e-06s
Believability | Calculation of trust value for Persée in RDF took 1.9550323486328125e-05s
INFO | --- Analysis for data-persee-fr took 1799.0557627677917s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.0517094135284424s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.3158528804779053s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.02156829833984375s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.0001239776611328125s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.2159347534179688e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 128.46585130691528s
Availability | SPARQL endpoint availability check for Open Data Web took 13.466155290603638s
Availability | VoID file availability check for Open Data Web took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.3364217281341553s
Reputation | Calculation of the PageRank for Open Data Web took 0.02104330062866211s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.361701965332031e-05s
Believability | Calculation of trust value for Open Data Web took 1.6927719116210938e-05s
INFO | --- Analysis for data.odw.tw took 125.64010977745056s
Availability | SPARQL endpoint availability check for DataFAQs took 6.818771362304688e-05s
Availability | VoID file availability check for DataFAQs took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.30751681327819824s
Reputation | Calculation of the PageRank for DataFAQs took 0.021401643753051758s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.457069396972656e-05s
Believability | Calculation of trust value for DataFAQs took 1.239776611328125e-05s
INFO | --- Analysis for datafaqs took 172.81698608398438s
Availability | SPARQL endpoint availability check for datahub took 4.744529724121094e-05s
Availability | VoID file availability check for datahub took 0.0007236003875732422s
Completeness | Calculation of interlinking completeness for datahub took 28.68455219268799s
Reputation | Calculation of the PageRank for datahub took 0.02220749855041504s
Interlinking | Calculation of Degree of Connection for datahub took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for datahub took 5.316734313964844e-05s
Believability | Calculation of trust value for datahub took 1.2874603271484375e-05s
INFO | --- Analysis for datahub took 188.78589153289795s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 4.553182601928711s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 23.395681619644165s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.021308183670043945s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 4.7206878662109375e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 1.3828277587890625e-05s
INFO | --- Analysis for datahub-kr-datamap took 156.23902559280396s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.4497697353363037s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0006868839263916016s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3125736713409424s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.021398067474365234s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 8.726119995117188e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.3113021850585938e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 29.21548867225647s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.270963191986084s
Availability | VoID file availability check for datos-artium-org took 0.0008165836334228516s
Completeness | Calculation of interlinking completeness for datos-artium-org took 30.278595447540283s
Reputation | Calculation of the PageRank for datos-artium-org took 0.02131342887878418s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00012373924255371094s
Believability | Calculation of trust value for datos-artium-org took 1.4543533325195312e-05s
INFO | --- Analysis for datos-artium-org took 301.3220133781433s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.8539068698883057s
Availability | VoID file availability check for Datos.bcn.cl took 0.00042891502380371094s
Extra | Recovery of all triples for Datos.bcn.cl took 38.11421823501587s
Performance | Total latancy measurement for Datos.bcn.cl took 6.07160496711731s
Amount of data | Number of triples check for Datos.bcn.cl took 4.263587713241577s
Interoperability | New terms check for Datos.bcn.cl took 3.857104778289795s
Versatility | Languages check for Datos.bcn.cl took 301.0177309513092s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.302541971206665s
Security | Check HTTPS for Datos.bcn.cl took 0.7486357688903809s
Interpretability | RDF structures check for Datos.bcn.cl took 1.2827155590057373s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2271270751953125s
Availability | RDF dump link check for Datos.bcn.cl took 1.2488110065460205s
License | MR license check for Datos.bcn.cl took 1.2406456470489502s
License | HR license check for Datos.bcn.cl took 92.89289236068726s
Amount of data | Number of property check for Datos.bcn.cl took 1.27040433883667s
Understandability | Number of label check for Datos.bcn.cl took 1.454909324645996s
Understandability | URI regex check for Datos.bcn.cl took 2.4381887912750244s
Understandability | Vocabs check for Datos.bcn.cl took 1.1833031177520752s
Verifiability | Authors check for Datos.bcn.cl took 1.238964557647705s
Verifiability | Publishers check for Datos.bcn.cl took 1.2282567024230957s
Performance | Throughput check for Datos.bcn.cl took 12.07483983039856s
Amount of data | Check the number of entities for Datos.bcn.cl took 7.104873657226562e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.2066624164581299s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.2035942077636719s
Interlinking | skos check for Datos.bcn.cl took 1.2125086784362793s
Interlinking | skos check for Datos.bcn.cl took 1.2083334922790527s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.2137131690979004s
Currency | Creation date check for Datos.bcn.cl took 2.478184223175049s
Currency | Modification date check for Datos.bcn.cl took 1.2457549571990967s
Rep.Conc. | URIs length for Datos.bcn.cl took 34.85195279121399s
Interoperability | New vocabularies check for Datos.bcn.cl took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.2035307884216309s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.217066764831543s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.200132131576538s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 27.606394052505493s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.321852445602417s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.272568941116333s
Consistency | Disjoint class check for Datos.bcn.cl took 1.1761455535888672s
Consistency | Check Misplaced properties for Datos.bcn.cl took 8.349729776382446s
Consistency | Misplaced classes for Datos.bcn.cl took 2.104402780532837s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 24.03598690032959s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.4208083152770996s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 7.876572370529175s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.3006563186645508s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.4410035610198975s
Security | Sign check for Datos.bcn.cl took 1.2233977317810059s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 7428.955548763275s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 21.284775972366333s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.028728485107421875s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 2.8848648071289062e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0008015632629394531s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 0.00014281272888183594s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 8.58306884765625e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 1.52587890625e-05s
INFO | --- Analysis for datos-bcn-cl took 8399.597257614136s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.6784110069274902s
Availability | VoID file availability check for datos.bne.es took 0.0007116794586181641s
Extra | Recovery of all triples for datos.bne.es took 142.25641298294067s
Performance | Total latancy measurement for datos.bne.es took 1.3560535907745361s
Amount of data | Number of triples check for datos.bne.es took 2.6002755165100098s
Interoperability | New terms check for datos.bne.es took 4.202739000320435s
Versatility | Languages check for datos.bne.es took 63.61338806152344s
Interpretability | Number of blank nodes check for datos.bne.es took 0.30655717849731445s
Security | Check HTTPS for datos.bne.es took 0.19682693481445312s
Interpretability | RDF structures check for datos.bne.es took 2.4014832973480225s
Versatility | Serialization formats check for datos.bne.es took 2.4526824951171875s
Availability | RDF dump link check for datos.bne.es took 2.167156457901001s
License | MR license check for datos.bne.es took 2.66973614692688s
License | HR license check for datos.bne.es took 60.93848943710327s
Amount of data | Number of property check for datos.bne.es took 0.32897186279296875s
Understandability | Number of label check for datos.bne.es took 2.862948417663574s
Understandability | URI regex check for datos.bne.es took 0.8340201377868652s
Understandability | Vocabs check for datos.bne.es took 0.3629467487335205s
Verifiability | Authors check for datos.bne.es took 0.4338810443878174s
Verifiability | Publishers check for datos.bne.es took 0.4095010757446289s
Performance | Throughput check for datos.bne.es took 23.813177585601807s
Amount of data | Check the number of entities for datos.bne.es took 8.463859558105469e-05s
Verifiability | Contribs. check for datos.bne.es took 0.37921786308288574s
Interlinking | sameAs chians check for datos.bne.es took 4.38116192817688s
Interlinking | skos check for datos.bne.es took 0.6481781005859375s
Interlinking | skos check for datos.bne.es took 0.32285022735595703s
Timeliness | dataset update frequency check for datos.bne.es took 0.4653503894805908s
Currency | Creation date check for datos.bne.es took 4.280380725860596s
Currency | Modification date check for datos.bne.es took 0.5965859889984131s
Rep.Conc. | URIs length for datos.bne.es took 58.287254095077515s
Interoperability | New vocabularies check for datos.bne.es took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 2.127155303955078s
Accuracy | Check Functional Property for datos.bne.es took 2.1628520488739014s
Accuracy | Check Inverse Functional Property for datos.bne.es took 0.3148837089538574s
Accuracy | Check Empty annotation labels for datos.bne.es took 41.406508684158325s
Accuracy | Check White space in annotation for datos.bne.es took 1.6201331615447998s
Accuracy | Check Datatype consistency for datos.bne.es took 1.3271138668060303s
Consistency | Disjoint class check for datos.bne.es took 2.163771629333496s
Consistency | Check Misplaced properties for datos.bne.es took 10.319567203521729s
Consistency | Misplaced classes for datos.bne.es took 4.493704795837402s
Consistency | Check Ontology hijacking for datos.bne.es took 43.965957164764404s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.4157321453094482s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 9.573487520217896s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.4182713031768799s
Conciseness | Check Intensional conciseness for datos.bne.es took 0.3215808868408203s
Security | Sign check for datos.bne.es took 1.1328926086425781s
Availability | Check URIs Dereferenciability for datos.bne.es took 9.937625646591187s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.3844451904296875s
Reputation | Calculation of the PageRank for datos.bne.es took 0.02155780792236328s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011944770812988281s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 1.9073486328125e-06s
Believability | Calculation of trust value for datos.bne.es took 8.58306884765625e-06s
INFO | --- Analysis for datos-bne-es took 802.5942494869232s
Availability | SPARQL endpoint availability check for dbacademic took 0.07501435279846191s
Availability | VoID file availability check for dbacademic took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for dbacademic took 0.3428347110748291s
Reputation | Calculation of the PageRank for dbacademic took 0.022812366485595703s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0008046627044677734s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.5762786865234375e-05s
Believability | Calculation of trust value for dbacademic took 9.775161743164062e-06s
INFO | --- Analysis for dbacademic took 83.71787285804749s
Availability | SPARQL endpoint availability check for DBkWik took 0.19689130783081055s
Availability | VoID file availability check for DBkWik took 0.0004444122314453125s
Extra | Recovery of all triples for DBkWik took 1.3549318313598633s
Performance | Total latancy measurement for DBkWik took 0.44884514808654785s
Amount of data | Number of triples check for DBkWik took 4.721134424209595s
Interoperability | New terms check for DBkWik took 2.19917368888855s
Versatility | Languages check for DBkWik took 61.58622336387634s
Interpretability | Number of blank nodes check for DBkWik took 0.12427926063537598s
Interpretability | RDF structures check for DBkWik took 0.27161288261413574s
Versatility | Serialization formats check for DBkWik took 0.27199411392211914s
Availability | RDF dump link check for DBkWik took 2.8197107315063477s
License | MR license check for DBkWik took 0.3966522216796875s
License | HR license check for DBkWik took 61.2443323135376s
Amount of data | Number of property check for DBkWik took 0.16012072563171387s
Understandability | Number of label check for DBkWik took 2.310120105743408s
Understandability | URI regex check for DBkWik took 0.336397647857666s
Understandability | Vocabs check for DBkWik took 0.11389923095703125s
Verifiability | Authors check for DBkWik took 0.11668133735656738s
Verifiability | Publishers check for DBkWik took 0.08255815505981445s
Performance | Throughput check for DBkWik took 10.480515480041504s
Amount of data | Check the number of entities for DBkWik took 0.00014734268188476562s
Verifiability | Contribs. check for DBkWik took 0.12824392318725586s
Interlinking | sameAs chians check for DBkWik took 0.4217369556427002s
Interlinking | skos check for DBkWik took 0.5197107791900635s
Interlinking | skos check for DBkWik took 0.07541012763977051s
Timeliness | dataset update frequency check for DBkWik took 0.22306489944458008s
Currency | Creation date check for DBkWik took 0.4688124656677246s
Currency | Modification date check for DBkWik took 0.192793607711792s
Rep.Conc. | URIs length for DBkWik took 11.30044174194336s
Interoperability | New vocabularies check for DBkWik took 9.311211824417114s
Consistency | Deprecated classes/propertiers check for DBkWik took 18.950925827026367s
Accuracy | Check Functional Property for DBkWik took 0.7328581809997559s
Accuracy | Check Inverse Functional Property for DBkWik took 0.3065478801727295s
Accuracy | Check Empty annotation labels for DBkWik took 1.1134922504425049s
Accuracy | Check White space in annotation for DBkWik took 0.023413658142089844s
Accuracy | Check Datatype consistency for DBkWik took 0.03867602348327637s
Consistency | Disjoint class check for DBkWik took 0.1145632266998291s
Consistency | Check Misplaced properties for DBkWik took 12.237735986709595s
Consistency | Misplaced classes for DBkWik took 0.5550987720489502s
Consistency | Check Ontology hijacking for DBkWik took 1.8761510848999023s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.380831241607666s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.773392677307129s
Conciseness | Check Extensional conciseness for DBkWik took 0.03360390663146973s
Conciseness | Check Intensional conciseness for DBkWik took 0.6845226287841797s
Security | Sign check for DBkWik took 0.2957181930541992s
Availability | Check URIs Dereferenciability for DBkWik took 9.6498863697052s
Completeness | Calculation of interlinking completeness for DBkWik took 0.3686027526855469s
Reputation | Calculation of the PageRank for DBkWik took 0.02130746841430664s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.2479248046875e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 11.18693208694458s
Believability | Calculation of trust value for DBkWik took 1.3113021850585938e-05s
INFO | --- Analysis for dbkwik took 1668.7346386909485s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 8.940696716308594e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.325366735458374s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.020732402801513672s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00011563301086425781s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 143.75273847579956s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.43079614639282227s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0006077289581298828s
Extra | Recovery of all triples for dblp Knowledge Graph took 7.165323495864868s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.8785603046417236s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.1546158790588379s
Interoperability | New terms check for dblp Knowledge Graph took 1.9288733005523682s
Versatility | Languages check for dblp Knowledge Graph took 0.1552274227142334s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 5.897223472595215s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.17246603965759277s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.18299245834350586s
Availability | RDF dump link check for dblp Knowledge Graph took 0.14766621589660645s
License | MR license check for dblp Knowledge Graph took 0.1429436206817627s
License | HR license check for dblp Knowledge Graph took 30.133081912994385s
Amount of data | Number of property check for dblp Knowledge Graph took 0.17052054405212402s
Understandability | Number of label check for dblp Knowledge Graph took 0.45334672927856445s
Understandability | URI regex check for dblp Knowledge Graph took 0.28141212463378906s
Understandability | Vocabs check for dblp Knowledge Graph took 0.150238037109375s
Verifiability | Authors check for dblp Knowledge Graph took 0.16450119018554688s
Verifiability | Publishers check for dblp Knowledge Graph took 0.16084003448486328s
Performance | Throughput check for dblp Knowledge Graph took 10.497352838516235s
Amount of data | Check the number of entities for dblp Knowledge Graph took 7.534027099609375e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.13939809799194336s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.18458127975463867s
Interlinking | skos check for dblp Knowledge Graph took 0.17665505409240723s
Interlinking | skos check for dblp Knowledge Graph took 0.14827322959899902s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.18137717247009277s
Currency | Creation date check for dblp Knowledge Graph took 0.35918688774108887s
Currency | Modification date check for dblp Knowledge Graph took 0.3437623977661133s
Rep.Conc. | URIs length for dblp Knowledge Graph took 15.245483875274658s
Interoperability | New vocabularies check for dblp Knowledge Graph took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.15587234497070312s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.1557466983795166s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.1317293643951416s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 7.599531173706055s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.1311466693878174s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.226553440093994s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.1495664119720459s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.34316396713256836s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 6.790199041366577s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 21237.18202996254s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 4.622708082199097s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.717993974685669s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.21372532844543457s
Security | Sign check for dblp Knowledge Graph took 0.15166258811950684s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 3.814943552017212s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.37053561210632324s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.021590471267700195s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.6927719116210938e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 1.9073486328125e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 1.239776611328125e-05s
INFO | --- Analysis for dblp-kg took 21448.936329603195s
Availability | SPARQL endpoint availability check for DBnary took 0.35980820655822754s
Availability | VoID file availability check for DBnary took 0.0005865097045898438s
Extra | Recovery of all triples for DBnary took 1.2548444271087646s
Performance | Total latancy measurement for DBnary took 0.3824002742767334s
Amount of data | Number of triples check for DBnary took 1.2945704460144043s
Interoperability | New terms check for DBnary took 3.7858023643493652s
Versatility | Languages check for DBnary took 60.21563458442688s
Interpretability | Number of blank nodes check for DBnary took 3.8646199703216553s
Security | Check HTTPS for DBnary took 0.18755221366882324s
Interpretability | RDF structures check for DBnary took 0.161149263381958s
Versatility | Serialization formats check for DBnary took 0.13684630393981934s
Availability | RDF dump link check for DBnary took 0.07353806495666504s
License | MR license check for DBnary took 0.20885992050170898s
License | HR license check for DBnary took 60.15229821205139s
Amount of data | Number of property check for DBnary took 0.11542677879333496s
Understandability | Number of label check for DBnary took 0.9780871868133545s
Understandability | URI regex check for DBnary took 0.18874073028564453s
Understandability | Vocabs check for DBnary took 0.11870026588439941s
Verifiability | Authors check for DBnary took 0.17594218254089355s
Verifiability | Publishers check for DBnary took 0.11938309669494629s
Performance | Throughput check for DBnary took 10.432226181030273s
Amount of data | Check the number of entities for DBnary took 7.200241088867188e-05s
Verifiability | Contribs. check for DBnary took 0.11529064178466797s
Interlinking | sameAs chians check for DBnary took 0.09929633140563965s
Interlinking | skos check for DBnary took 0.13840317726135254s
Interlinking | skos check for DBnary took 0.10200691223144531s
Timeliness | dataset update frequency check for DBnary took 0.14602160453796387s
Currency | Creation date check for DBnary took 0.22518539428710938s
Currency | Modification date check for DBnary took 0.19968247413635254s
Rep.Conc. | URIs length for DBnary took 11.125978708267212s
Interoperability | New vocabularies check for DBnary took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for DBnary took 0.10177373886108398s
Accuracy | Check Functional Property for DBnary took 0.1900463104248047s
Accuracy | Check Inverse Functional Property for DBnary took 0.14508318901062012s
Accuracy | Check Empty annotation labels for DBnary took 0.43050694465637207s
Accuracy | Check White space in annotation for DBnary took 0.02521824836730957s
Accuracy | Check Datatype consistency for DBnary took 0.029472827911376953s
Consistency | Disjoint class check for DBnary took 0.27362966537475586s
Consistency | Check Misplaced properties for DBnary took 8.695130825042725s
Consistency | Misplaced classes for DBnary took 0.2419130802154541s
Consistency | Check Ontology hijacking for DBnary took 2.0705504417419434s
Consistency | Check Invalid usage of undefined classes for DBnary took 1.6534066200256348s
Consistency | Check Invalid usage of undefined properties for DBnary took 10.196959257125854s
Conciseness | Check Extensional conciseness for DBnary took 0.03769636154174805s
Conciseness | Check Intensional conciseness for DBnary took 0.19426655769348145s
Security | Sign check for DBnary took 0.067230224609375s
Availability | Check URIs Dereferenciability for DBnary took 9.686859369277954s
Completeness | Calculation of interlinking completeness for DBnary took 0.40535402297973633s
Reputation | Calculation of the PageRank for DBnary took 0.021265506744384766s
Interlinking | Calculation of Degree of Connection for DBnary took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for DBnary took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for DBnary took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for DBnary took 1.430511474609375e-06s
Believability | Calculation of trust value for DBnary took 1.2874603271484375e-05s
INFO | --- Analysis for dbnary took 477.81503200531006s
Availability | SPARQL endpoint availability check for DBpedia took 0.9600026607513428s
Availability | VoID file availability check for DBpedia took 0.0007498264312744141s
Extra | Recovery of all triples for DBpedia took 3.435096502304077s
Performance | Total latancy measurement for DBpedia took 2.886388063430786s
Amount of data | Number of triples check for DBpedia took 2.110173463821411s
Interoperability | New terms check for DBpedia took 6.327861547470093s
Versatility | Languages check for DBpedia took 31.770379781723022s
Interpretability | Number of blank nodes check for DBpedia took 0.5690474510192871s
Security | Check HTTPS for DBpedia took 0.31934285163879395s
Interpretability | RDF structures check for DBpedia took 0.8218276500701904s
Versatility | Serialization formats check for DBpedia took 1.1324775218963623s
Availability | RDF dump link check for DBpedia took 0.5822188854217529s
License | MR license check for DBpedia took 0.9268901348114014s
License | HR license check for DBpedia took 32.190077781677246s
Amount of data | Number of property check for DBpedia took 0.6438624858856201s
Understandability | Number of label check for DBpedia took 22.432595252990723s
Understandability | URI regex check for DBpedia took 1.2204780578613281s
Understandability | Vocabs check for DBpedia took 0.6843166351318359s
Verifiability | Authors check for DBpedia took 0.7700037956237793s
Verifiability | Publishers check for DBpedia took 0.6794993877410889s
Performance | Throughput check for DBpedia took 11.395488023757935s
Amount of data | Check the number of entities for DBpedia took 8.678436279296875e-05s
Verifiability | Contribs. check for DBpedia took 0.6999742984771729s
Interlinking | sameAs chians check for DBpedia took 7.707168340682983s
Interlinking | skos check for DBpedia took 0.643338680267334s
Interlinking | skos check for DBpedia took 0.5616812705993652s
Timeliness | dataset update frequency check for DBpedia took 0.6894187927246094s
Currency | Creation date check for DBpedia took 1.3425798416137695s
Currency | Modification date check for DBpedia took 1.3180205821990967s
Rep.Conc. | URIs length for DBpedia took 41.52349519729614s
Interoperability | New vocabularies check for DBpedia took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.5899710655212402s
Accuracy | Check Functional Property for DBpedia took 0.6400418281555176s
Accuracy | Check Inverse Functional Property for DBpedia took 0.5892486572265625s
Accuracy | Check Empty annotation labels for DBpedia took 2.6144447326660156s
Accuracy | Check White space in annotation for DBpedia took 0.02939629554748535s
Accuracy | Check Datatype consistency for DBpedia took 0.028939485549926758s
Consistency | Disjoint class check for DBpedia took 0.5747029781341553s
Consistency | Check Misplaced properties for DBpedia took 35.59367895126343s
Consistency | Misplaced classes for DBpedia took 6.119516611099243s
Consistency | Check Ontology hijacking for DBpedia took 6.846115350723267s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.3557870388031006s
Consistency | Check Invalid usage of undefined properties for DBpedia took 2.7783596515655518s
Conciseness | Check Extensional conciseness for DBpedia took 0.03340315818786621s
Conciseness | Check Intensional conciseness for DBpedia took 8.808809757232666s
Security | Sign check for DBpedia took 0.6154115200042725s
Availability | Check URIs Dereferenciability for DBpedia took 4720.7769339084625s
Completeness | Calculation of interlinking completeness for DBpedia took 0.30561232566833496s
Reputation | Calculation of the PageRank for DBpedia took 0.022754669189453125s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0009670257568359375s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.9073486328125e-06s
Believability | Calculation of trust value for DBpedia took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia took 7376.046374082565s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.482269287109375e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 22.18460202217102s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.021159887313842773s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 7.486343383789062e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.1444091796875e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 127.5071849822998s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.181075811386108s
Availability | VoID file availability check for DBpedia Commons took 0.0007474422454833984s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.391099214553833s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.021666765213012695s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 7.200241088867188e-05s
Believability | Calculation of trust value for DBpedia Commons took 1.239776611328125e-05s
INFO | --- Analysis for dbpedia-commons took 73.4690957069397s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 0.37325263023376465s
Availability | VoID file availability check for DBpedia in Greek took 0.0005345344543457031s
Extra | Recovery of all triples for DBpedia in Greek took 1.4290566444396973s
Performance | Total latancy measurement for DBpedia in Greek took 1.205432415008545s
Amount of data | Number of triples check for DBpedia in Greek took 0.3450508117675781s
Interoperability | New terms check for DBpedia in Greek took 1.7462408542633057s
Versatility | Languages check for DBpedia in Greek took 11.895981788635254s
Interpretability | Number of blank nodes check for DBpedia in Greek took 0.21656203269958496s
Security | Check HTTPS for DBpedia in Greek took 0.1429152488708496s
Interpretability | RDF structures check for DBpedia in Greek took 0.29615139961242676s
Versatility | Serialization formats check for DBpedia in Greek took 0.2602846622467041s
Availability | RDF dump link check for DBpedia in Greek took 0.2388746738433838s
License | MR license check for DBpedia in Greek took 0.2711968421936035s
License | HR license check for DBpedia in Greek took 2.6532785892486572s
Amount of data | Number of property check for DBpedia in Greek took 0.2398386001586914s
Understandability | Number of label check for DBpedia in Greek took 0.3248727321624756s
Understandability | URI regex check for DBpedia in Greek took 0.5003292560577393s
Understandability | Vocabs check for DBpedia in Greek took 0.2605936527252197s
Verifiability | Authors check for DBpedia in Greek took 0.24007034301757812s
Verifiability | Publishers check for DBpedia in Greek took 0.2465968132019043s
Performance | Throughput check for DBpedia in Greek took 11.820330381393433s
Amount of data | Check the number of entities for DBpedia in Greek took 7.843971252441406e-05s
Verifiability | Contribs. check for DBpedia in Greek took 0.2823946475982666s
Interlinking | sameAs chians check for DBpedia in Greek took 0.28539466857910156s
Interlinking | skos check for DBpedia in Greek took 0.4322633743286133s
Interlinking | skos check for DBpedia in Greek took 0.24478554725646973s
Timeliness | dataset update frequency check for DBpedia in Greek took 0.3367180824279785s
Currency | Creation date check for DBpedia in Greek took 0.4852325916290283s
Currency | Modification date check for DBpedia in Greek took 0.4560067653656006s
Rep.Conc. | URIs length for DBpedia in Greek took 1.8183906078338623s
Interoperability | New vocabularies check for DBpedia in Greek took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Greek took 0.23587465286254883s
Accuracy | Check Functional Property for DBpedia in Greek took 0.23921775817871094s
Accuracy | Check Inverse Functional Property for DBpedia in Greek took 0.2510991096496582s
Accuracy | Check Empty annotation labels for DBpedia in Greek took 0.7010369300842285s
Accuracy | Check White space in annotation for DBpedia in Greek took 0.03148293495178223s
Accuracy | Check Datatype consistency for DBpedia in Greek took 0.02939629554748535s
Consistency | Disjoint class check for DBpedia in Greek took 0.22433257102966309s
Consistency | Check Misplaced properties for DBpedia in Greek took 1.3936841487884521s
Consistency | Misplaced classes for DBpedia in Greek took 0.7492659091949463s
Consistency | Check Ontology hijacking for DBpedia in Greek took 2.005537986755371s
Consistency | Check Invalid usage of undefined classes for DBpedia in Greek took 1.3772573471069336s
Consistency | Check Invalid usage of undefined properties for DBpedia in Greek took 2.327450752258301s
Conciseness | Check Extensional conciseness for DBpedia in Greek took 0.035546064376831055s
Conciseness | Check Intensional conciseness for DBpedia in Greek took 0.7819006443023682s
Security | Sign check for DBpedia in Greek took 0.2587471008300781s
Availability | Check URIs Dereferenciability for DBpedia in Greek took 2080.627277135849s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.805938720703125s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.022106409072875977s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.0002162456512451172s
Interoperability | Check the re-using of existing vocabs for DBpedia in Greek took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia in Greek took 1.239776611328125e-05s
INFO | --- Analysis for dbpedia-el took 2248.8335757255554s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 2.4700987339019775s
Availability | VoID file availability check for DBpedia in Spanish took 0.0007660388946533203s
Extra | Recovery of all triples for DBpedia in Spanish took 2.6994996070861816s
Performance | Total latancy measurement for DBpedia in Spanish took 1.2046699523925781s
Amount of data | Number of triples check for DBpedia in Spanish took 0.8462255001068115s
Interoperability | New terms check for DBpedia in Spanish took 3.0061590671539307s
Versatility | Languages check for DBpedia in Spanish took 60.32173228263855s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.36811304092407227s
Security | Check HTTPS for DBpedia in Spanish took 0.1398472785949707s
Interpretability | RDF structures check for DBpedia in Spanish took 1.5154266357421875s
Versatility | Serialization formats check for DBpedia in Spanish took 0.59610915184021s
Availability | RDF dump link check for DBpedia in Spanish took 0.3714566230773926s
License | MR license check for DBpedia in Spanish took 0.8265354633331299s
License | HR license check for DBpedia in Spanish took 60.67863178253174s
Amount of data | Number of property check for DBpedia in Spanish took 0.31931638717651367s
Understandability | Number of label check for DBpedia in Spanish took 1.9089515209197998s
Understandability | URI regex check for DBpedia in Spanish took 0.8053650856018066s
Understandability | Vocabs check for DBpedia in Spanish took 0.38913393020629883s
Verifiability | Authors check for DBpedia in Spanish took 0.3122737407684326s
Verifiability | Publishers check for DBpedia in Spanish took 0.30754971504211426s
Performance | Throughput check for DBpedia in Spanish took 11.545776844024658s
Amount of data | Check the number of entities for DBpedia in Spanish took 4.839897155761719e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.2960548400878906s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.6078002452850342s
Interlinking | skos check for DBpedia in Spanish took 0.637242317199707s
Interlinking | skos check for DBpedia in Spanish took 0.23603487014770508s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.4269683361053467s
Currency | Creation date check for DBpedia in Spanish took 0.6209030151367188s
Currency | Modification date check for DBpedia in Spanish took 0.5879533290863037s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.424247980117798s
Interoperability | New vocabularies check for DBpedia in Spanish took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.30556750297546387s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.46442699432373047s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.45313334465026855s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 0.9810874462127686s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.031888723373413086s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.034899234771728516s
Consistency | Disjoint class check for DBpedia in Spanish took 0.2929065227508545s
Consistency | Check Misplaced properties for DBpedia in Spanish took 7.997685670852661s
Consistency | Misplaced classes for DBpedia in Spanish took 1.0701265335083008s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.4850165843963623s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.3630297183990479s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 7.151790618896484s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03464984893798828s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.679593801498413s
Security | Sign check for DBpedia in Spanish took 0.32247090339660645s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 3.085355281829834s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 27.148671865463257s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.021851062774658203s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00011420249938964844s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 1.3589859008789062e-05s
INFO | --- Analysis for dbpedia-es took 1245.2158653736115s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.175534725189209s
Availability | VoID file availability check for DBpedia in Basque took 0.00042748451232910156s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.29219651222229004s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.022610187530517578s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007977485656738281s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.4809112548828125e-05s
Believability | Calculation of trust value for DBpedia in Basque took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia-eu took 152.02566719055176s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.15205121040344238s
Availability | VoID file availability check for DBpedia in French took 0.0007877349853515625s
Extra | Recovery of all triples for DBpedia in French took 88.78849220275879s
Performance | Total latancy measurement for DBpedia in French took 0.4241628646850586s
Amount of data | Number of triples check for DBpedia in French took 1.569310188293457s
Interoperability | New terms check for DBpedia in French took 2.655869483947754s
Versatility | Languages check for DBpedia in French took 300.09466767311096s
Interpretability | Number of blank nodes check for DBpedia in French took 0.18256092071533203s
Security | Check HTTPS for DBpedia in French took 0.2037794589996338s
Interpretability | RDF structures check for DBpedia in French took 0.636317253112793s
Versatility | Serialization formats check for DBpedia in French took 0.44022345542907715s
Availability | RDF dump link check for DBpedia in French took 6.795960903167725s
License | MR license check for DBpedia in French took 2.0357344150543213s
License | HR license check for DBpedia in French took 81.77810502052307s
Amount of data | Number of property check for DBpedia in French took 0.16114449501037598s
Understandability | Number of label check for DBpedia in French took 1.5608043670654297s
Understandability | URI regex check for DBpedia in French took 0.31329989433288574s
Understandability | Vocabs check for DBpedia in French took 0.16739654541015625s
Verifiability | Authors check for DBpedia in French took 0.3096160888671875s
Verifiability | Publishers check for DBpedia in French took 0.15075111389160156s
Performance | Throughput check for DBpedia in French took 10.544727563858032s
Amount of data | Check the number of entities for DBpedia in French took 2.331399917602539s
Verifiability | Contribs. check for DBpedia in French took 0.14954018592834473s
Interlinking | sameAs chians check for DBpedia in French took 0.3978760242462158s
Interlinking | skos check for DBpedia in French took 0.24329328536987305s
Interlinking | skos check for DBpedia in French took 0.07803583145141602s
Timeliness | dataset update frequency check for DBpedia in French took 0.3560018539428711s
Currency | Creation date check for DBpedia in French took 0.26492786407470703s
Currency | Modification date check for DBpedia in French took 0.20818066596984863s
Rep.Conc. | URIs length for DBpedia in French took 41.281747579574585s
Interoperability | New vocabularies check for DBpedia in French took 11.662896871566772s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.1006174087524414s
Accuracy | Check Functional Property for DBpedia in French took 0.15370559692382812s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.10882019996643066s
Accuracy | Check Empty annotation labels for DBpedia in French took 33.74385404586792s
Accuracy | Check White space in annotation for DBpedia in French took 3.136855125427246s
Accuracy | Check Datatype consistency for DBpedia in French took 2.70412015914917s
Consistency | Disjoint class check for DBpedia in French took 0.3104538917541504s
Consistency | Check Misplaced properties for DBpedia in French took 7.491022825241089s
Consistency | Misplaced classes for DBpedia in French took 9.634482145309448s
Consistency | Check Ontology hijacking for DBpedia in French took 21.381622791290283s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.489217758178711s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 7.778501033782959s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.0244312286376953s
Conciseness | Check Intensional conciseness for DBpedia in French took 2.114744186401367s
Security | Sign check for DBpedia in French took 0.12758779525756836s
Availability | Check URIs Dereferenciability for DBpedia in French took 2168.8125054836273s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.8221211433410645s
Reputation | Calculation of the PageRank for DBpedia in French took 0.021853208541870117s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00015401840209960938s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 40.46605920791626s
Believability | Calculation of trust value for DBpedia in French took 9.059906005859375e-06s
INFO | --- Analysis for dbpedia-fr took 3152.376490354538s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.933107852935791s
Availability | VoID file availability check for DBpedia in Japanese took 4.017310619354248s
Extra | Recovery of all triples for DBpedia in Japanese took 5.528783082962036s
Performance | Total latancy measurement for DBpedia in Japanese took 6.665327548980713s
Amount of data | Number of triples check for DBpedia in Japanese took 121.34440660476685s
Interoperability | New terms check for DBpedia in Japanese took 19.402304887771606s
Versatility | Languages check for DBpedia in Japanese took 1.3300285339355469s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3192353248596191s
Security | Check HTTPS for DBpedia in Japanese took 0.8004357814788818s
Interpretability | RDF structures check for DBpedia in Japanese took 1.7205541133880615s
Versatility | Serialization formats check for DBpedia in Japanese took 1.7223832607269287s
Availability | RDF dump link check for DBpedia in Japanese took 1.32792067527771s
License | MR license check for DBpedia in Japanese took 1.6972646713256836s
License | HR license check for DBpedia in Japanese took 121.32338380813599s
Amount of data | Number of property check for DBpedia in Japanese took 1.341191291809082s
Understandability | Number of label check for DBpedia in Japanese took 9.854619026184082s
Understandability | URI regex check for DBpedia in Japanese took 2.6844677925109863s
Understandability | Vocabs check for DBpedia in Japanese took 1.468231439590454s
Verifiability | Authors check for DBpedia in Japanese took 1.3371882438659668s
Verifiability | Publishers check for DBpedia in Japanese took 1.3973708152770996s
Performance | Throughput check for DBpedia in Japanese took 13.34828782081604s
Amount of data | Check the number of entities for DBpedia in Japanese took 7.414817810058594e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3393933773040771s
Interlinking | sameAs chians check for DBpedia in Japanese took 3.2849700450897217s
Interlinking | skos check for DBpedia in Japanese took 1.8304643630981445s
Interlinking | skos check for DBpedia in Japanese took 1.946930170059204s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.3512990474700928s
Currency | Creation date check for DBpedia in Japanese took 2.848233222961426s
Currency | Modification date check for DBpedia in Japanese took 2.6896352767944336s
Rep.Conc. | URIs length for DBpedia in Japanese took 139.220929145813s
Interoperability | New vocabularies check for DBpedia in Japanese took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3420913219451904s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 2.968492269515991s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.026335716247558594s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.02979135513305664s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4563348293304443s
Consistency | Check Misplaced properties for DBpedia in Japanese took 122.69221425056458s
Consistency | Misplaced classes for DBpedia in Japanese took 3.0201807022094727s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.460665702819824s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.5032074451446533s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 122.86318969726562s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.034897804260253906s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 3.464284658432007s
Security | Sign check for DBpedia in Japanese took 1.3568873405456543s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 8.755779504776001s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 22.08051609992981s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.02157759666442871s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00011515617370605469s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-ja took 1472.8206913471222s
Availability | SPARQL endpoint availability check for dbpedia lite took 6.842613220214844e-05s
Availability | VoID file availability check for dbpedia lite took 0.0007195472717285156s
Completeness | Calculation of interlinking completeness for dbpedia lite took 22.0730299949646s
Reputation | Calculation of the PageRank for dbpedia lite took 0.021993637084960938s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0008935928344726562s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.0001354217529296875s
Believability | Calculation of trust value for dbpedia lite took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia-lite took 150.6462857723236s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.2242734432220459s
Availability | VoID file availability check for DBpedia in Dutch took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 27.515321493148804s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.023325681686401367s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0008344650268554688s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00019598007202148438s
Believability | Calculation of trust value for DBpedia in Dutch took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-nl took 157.62356734275818s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 4.490592956542969s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.31972336769104004s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.02174997329711914s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0010614395141601562s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 0.00011897087097167969s
Believability | Calculation of trust value for DBpedia in Portuguese took 1.1682510375976562e-05s
INFO | --- Analysis for dbpedia-pt took 119.73911595344543s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 0.00017142295837402344s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0008711814880371094s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 27.73507785797119s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.021581172943115234s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0010540485382080078s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 8.916854858398438e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 121.48761653900146s
Availability | SPARQL endpoint availability check for DBTropes took 4.410743713378906e-05s
Availability | VoID file availability check for DBTropes took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for DBTropes took 29.55030107498169s
Reputation | Calculation of the PageRank for DBTropes took 0.021813392639160156s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0008385181427001953s
Interlinking | Calculation of Clustering coefficient for DBTropes took 0.00010514259338378906s
Believability | Calculation of trust value for DBTropes took 7.867813110351562e-06s
INFO | --- Analysis for dbtropes took 61.70673847198486s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 9.036064147949219e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 28.076993465423584s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020996809005737305s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.745887756347656e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 1.1444091796875e-05s
INFO | --- Analysis for dbtune-artists-last-fm took 112.40740299224854s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 9.274482727050781e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.2912638187408447s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.021426916122436523s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 4.00543212890625e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.1682510375976562e-05s
INFO | --- Analysis for dbtune-audioscrobbler took 57.99503540992737s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.727853536605835s
Availability | VoID file availability check for DBTune.org/classical took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.38214707374572754s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.02112746238708496s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 8.821487426757812e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.239776611328125e-05s
INFO | --- Analysis for dbtune-classical took 117.4923324584961s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 0.29410886764526367s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.30786609649658203s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.021503448486328125s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0011181831359863281s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 9.560585021972656e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 1.1682510375976562e-05s
INFO | --- Analysis for dbtune-john-peel-sessions took 106.36832571029663s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 0.28214550018310547s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0008790493011474609s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.31914639472961426s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.021076679229736328s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 7.653236389160156e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.239776611328125e-05s
INFO | --- Analysis for dbtune-magnatune took 55.15708017349243s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 180.45879364013672s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0007655620574951172s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.31200361251831055s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.021352052688598633s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.0001246929168701172s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.1682510375976562e-05s
INFO | --- Analysis for dbtune-musicbrainz took 478.29791474342346s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.3314340114593506s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 25.27489447593689s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.021073102951049805s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 6.246566772460938e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.1920928955078125e-05s
INFO | --- Analysis for dbtune-myspace took 119.93688297271729s
Availability | SPARQL endpoint availability check for data.dcs took 0.00010633468627929688s
Availability | VoID file availability check for data.dcs took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for data.dcs took 26.785526514053345s
Reputation | Calculation of the PageRank for data.dcs took 0.022012948989868164s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.000858306884765625s
Interlinking | Calculation of Clustering coefficient for data.dcs took 8.082389831542969e-05s
Believability | Calculation of trust value for data.dcs took 1.1444091796875e-05s
INFO | --- Analysis for dcs-sheffield took 141.11534428596497s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 0.0001049041748046875s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 20.76966953277588s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.021430253982543945s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 4.5299530029296875e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 7.3909759521484375e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 147.78016996383667s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.649162292480469e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 25.625691890716553s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.02301955223083496s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0008361339569091797s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 5.91278076171875e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.1444091796875e-05s
INFO | --- Analysis for debian-package-tracking-system took 170.4269700050354s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 9.465217590332031e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.4321775436401367s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.02114391326904297s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 4.0531158447265625e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.33514404296875e-05s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 204.37768959999084s
Availability | SPARQL endpoint availability check for Demografie took 4.506111145019531e-05s
Availability | VoID file availability check for Demografie took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Demografie took 0.3367772102355957s
Reputation | Calculation of the PageRank for Demografie took 0.020862340927124023s
Interlinking | Calculation of Degree of Connection for Demografie took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Demografie took 3.4809112548828125e-05s
Believability | Calculation of trust value for Demografie took 1.5020370483398438e-05s
INFO | --- Analysis for demografie took 100.49404001235962s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 0.4759523868560791s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 28.10438108444214s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.023644208908081055s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.001201629638671875s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 5.984306335449219e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 7.3909759521484375e-06s
INFO | --- Analysis for desaparecidos took 155.3694281578064s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.458427429199219e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 22.49403691291809s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.02085113525390625s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.00010967254638671875s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.3113021850585938e-05s
INFO | --- Analysis for deustoentrepreneurship took 150.94434475898743s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.553794860839844e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.9946737289428711s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 23.015705585479736s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.021245956420898438s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.0001232624053955078s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.6689300537109375e-05s
INFO | --- Analysis for deustotech took 117.28369164466858s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.4453861713409424s
Availability | VoID file availability check for Deutsche Biographie took 0.0013093948364257812s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 26.060004949569702s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.021018028259277344s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.029273986816406e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.1444091796875e-05s
INFO | --- Analysis for deutsche-biographie took 133.49427962303162s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 5.125999450683594e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 27.988192558288574s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.021364450454711914s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0008435249328613281s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 6.604194641113281e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 7.867813110351562e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 154.38432621955872s
Availability | SPARQL endpoint availability check for dev8d took 9.059906005859375e-05s
Availability | VoID file availability check for dev8d took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for dev8d took 24.567983150482178s
Reputation | Calculation of the PageRank for dev8d took 0.02216506004333496s
Interlinking | Calculation of Degree of Connection for dev8d took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for dev8d took 7.796287536621094e-05s
Believability | Calculation of trust value for dev8d took 1.1920928955078125e-05s
INFO | --- Analysis for dev8d took 99.09541964530945s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.23028540611267s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0011730194091796875s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 21.821650505065918s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.021109580993652344s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.841255187988281e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.2874603271484375e-05s
INFO | --- Analysis for dewey_decimal_classification took 290.39292669296265s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 9.250640869140625e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 25.67886757850647s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.021834135055541992s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.7670135498046875e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 1.1682510375976562e-05s
INFO | --- Analysis for DHSVM took 219.60987281799316s
Availability | SPARQL endpoint availability check for Diavgeia took 4.38690185546875e-05s
Availability | VoID file availability check for Diavgeia took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.49672627449035645s
Reputation | Calculation of the PageRank for Diavgeia took 0.02135634422302246s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 9.72747802734375e-05s
Believability | Calculation of trust value for Diavgeia took 9.5367431640625e-06s
INFO | --- Analysis for diavgeia took 142.11275601387024s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00016236305236816406s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.40961742401123047s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.022418737411499023s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00013399124145507812s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.363059997558594e-05s
INFO | --- Analysis for didactalia took 61.618634939193726s
Availability | SPARQL endpoint availability check for DisGeNET took 2.179844856262207s
Availability | VoID file availability check for DisGeNET took 0.0008087158203125s
Completeness | Calculation of interlinking completeness for DisGeNET took 23.41233801841736s
Reputation | Calculation of the PageRank for DisGeNET took 0.021164894104003906s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00018548965454101562s
Believability | Calculation of trust value for DisGeNET took 1.1205673217773438e-05s
INFO | --- Analysis for disgenet took 142.67105531692505s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 5.698204040527344e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.2909078598022461s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.021985292434692383s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 3.409385681152344e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 8.344650268554688e-06s
INFO | --- Analysis for distritos-zaragoza took 54.86569833755493s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.4345855712890625e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0007195472717285156s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 29.83274531364441s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.02118682861328125s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.266334533691406e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.2874603271484375e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 112.32736897468567s
Availability | SPARQL endpoint availability check for DM2E took 0.0001010894775390625s
Availability | VoID file availability check for DM2E took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for DM2E took 0.2878835201263428s
Reputation | Calculation of the PageRank for DM2E took 0.021040916442871094s
Interlinking | Calculation of Degree of Connection for DM2E took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00011372566223144531s
Believability | Calculation of trust value for DM2E took 1.2874603271484375e-05s
INFO | --- Analysis for dm2e took 81.52744555473328s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 4.38690185546875e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.00063323974609375s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 25.97057294845581s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020987749099731445s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.0001709461212158203s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 7.152557373046875e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 112.15879774093628s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 8.893013000488281e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0008089542388916016s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.4094717502593994s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.021443843841552734s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.771087646484375e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 9.298324584960938e-06s
INFO | --- Analysis for doi took 55.56821322441101s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.38690185546875e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.3661940097808838s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.02519845962524414s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.457069396972656e-05s
Believability | Calculation of trust value for Driggu Florentino took 7.3909759521484375e-06s
INFO | --- Analysis for Driggu took 128.97994565963745s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.37810611724853516s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 21.122973918914795s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.021465539932250977s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 4.7206878662109375e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.3828277587890625e-05s
INFO | --- Analysis for drug-data-hifm took 167.60773968696594s
Availability | SPARQL endpoint availability check for dspace took 4.2438507080078125e-05s
Availability | VoID file availability check for dspace took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for dspace took 0.2900705337524414s
Reputation | Calculation of the PageRank for dspace took 0.022016525268554688s
Interlinking | Calculation of Degree of Connection for dspace took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for dspace took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for dspace took 3.314018249511719e-05s
Believability | Calculation of trust value for dspace took 1.2636184692382812e-05s
INFO | --- Analysis for dspace took 100.83044981956482s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.5260922908783s
Availability | VoID file availability check for MetaLex Document Server took 0.0007374286651611328s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.3363370895385742s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.021218538284301758s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 4.887580871582031e-05s
Believability | Calculation of trust value for MetaLex Document Server took 1.1444091796875e-05s
INFO | --- Analysis for dutch-national-regulations-metalex took 631.6397566795349s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.4398069381713867s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 26.772316217422485s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.022304534912109375s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 5.555152893066406e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 7.62939453125e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 176.23605704307556s
Availability | SPARQL endpoint availability check for DWS-Group took 4.553794860839844e-05s
Availability | VoID file availability check for DWS-Group took 0.0003027915954589844s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.3384842872619629s
Reputation | Calculation of the PageRank for DWS-Group took 0.020966768264770508s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010561943054199219s
Believability | Calculation of trust value for DWS-Group took 8.58306884765625e-06s
INFO | --- Analysis for dws-group took 47.73846983909607s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.38690185546875e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 25.93457841873169s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.021152019500732422s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.24249267578125e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.1920928955078125e-05s
INFO | --- Analysis for E1 took 103.48815751075745s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.06904172897338867s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 27.13655376434326s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.027212142944335938s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00012755393981933594s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-alaska took 148.5996069908142s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.0476834774017334s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 24.38982844352722s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.02133941650390625s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 7.2479248046875e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-cau took 69.84849834442139s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.07179641723632812s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.37502408027648926s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.02097797393798828s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 7.128715515136719e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 3.030195474624634s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.047493696212768555s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 22.813316345214844s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.020947933197021484s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 0.00013017654418945312s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-cdrewu took 155.6939287185669s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.0708611011505127s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.38471412658691406s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.021384477615356445s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0008392333984375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00015044212341308594s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-dartmouth took 24.761839628219604s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.04670286178588867s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.28939342498779297s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02106308937072754s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.821487426757812e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-famu took 47.75744819641113s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.0412752628326416s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.3313486576080322s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.02103877067565918s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00013113021850585938s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-harvard took 129.5425033569336s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.04684567451477051s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 24.6057767868042s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.022708892822265625s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0009670257568359375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.0001621246337890625s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-hawaii took 81.90447163581848s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.04438161849975586s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.300612211227417s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.021502017974853516s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 8.058547973632812e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-howard took 49.79120993614197s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.047181129455566406s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 24.72715663909912s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.510185241699219e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 128.74615359306335s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.055388450622558594s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.3188905715942383s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.021056413650512695s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011944770812988281s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.0013580322265625e-05s
INFO | --- Analysis for eagle-i-jsu took 70.19064140319824s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.06049680709838867s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 22.575709104537964s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.02100348472595215s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 4.0531158447265625e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-meharry took 102.23623251914978s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.06700444221496582s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0003101825714111328s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2912001609802246s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.021151065826416016s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.0001087188720703125s
Believability | Calculation of trust value for eagle-i @ Montana State University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-montana took 50.42518639564514s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.049249887466430664s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.29656457901000977s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.021972179412841797s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0008258819580078125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 0.00010919570922851562s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-msm took 103.48790192604065s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.04256749153137207s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.32807397842407227s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.021904945373535156s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00014853477478027344s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-ohsu took 48.78288650512695s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.05913281440734863s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2776916027069092s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.021134138107299805s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0008161067962646484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 7.176399230957031e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-psm took 77.94746398925781s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.045213937759399414s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 25.545509576797485s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.02097320556640625s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.556510925292969e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-tsu took 125.00773358345032s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.040380239486694336s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.32388758659362793s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.021181583404541016s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.580352783203125e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-tuskegee took 72.57134509086609s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.0323643684387207s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.35922813415527344s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.021528005599975586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0008244514465332031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.0001285076141357422s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 2.2172927856445312e-05s
INFO | --- Analysis for eagle-i-uccaribe took 127.93139028549194s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.04695892333984375s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.31054043769836426s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.021221399307250977s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00013709068298339844s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-upr took 75.7020616531372s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.04450821876525879s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0003113746643066406s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.3535482883453369s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.021201610565185547s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.937980651855469e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-utep took 78.88498187065125s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.04005932807922363s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 25.805623054504395s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.023631811141967773s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.390975952148438e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.7642974853515625e-05s
INFO | --- Analysis for eagle-i-utsa took 128.9480335712433s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.15317726135253906s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.00030922889709472656s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.30999231338500977s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.021238088607788086s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 0.00010800361633300781s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 49.34730648994446s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.038308143615722656s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.3009979724884033s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.02279186248779297s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.581710815429688e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-xula took 70.75576114654541s
Availability | SPARQL endpoint availability check for Emergency situation took 0.6334304809570312s
Availability | VoID file availability check for Emergency situation took 0.0007910728454589844s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.3025529384613037s
Reputation | Calculation of the PageRank for Emergency situation took 0.02122044563293457s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 5.2928924560546875e-05s
Believability | Calculation of trust value for Emergency situation took 1.1682510375976562e-05s
INFO | --- Analysis for Earthquake took 105.08976221084595s
Availability | SPARQL endpoint availability check for ESO took 5.302300214767456s
Availability | VoID file availability check for ESO took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for ESO took 0.29115939140319824s
Reputation | Calculation of the PageRank for ESO took 0.021213293075561523s
Interlinking | Calculation of Degree of Connection for ESO took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for ESO took 8.678436279296875e-05s
Believability | Calculation of trust value for ESO took 7.62939453125e-06s
INFO | --- Analysis for Earthquake_case took 80.0917489528656s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.10892653465270996s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 28.59379482269287s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.02112412452697754s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00012063980102539062s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for ecb-linked-data took 132.24112176895142s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 5.825194597244263s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.4440333843231201s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.021336078643798828s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.695487976074219e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 9.775161743164062e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 106.6716525554657s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.7047176361083984s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.38553500175476074s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.021968841552734375s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 8.034706115722656e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 86.43348455429077s
Availability | SPARQL endpoint availability check for ECLAP took 20.33061933517456s
Availability | VoID file availability check for ECLAP took 0.0007557868957519531s
Completeness | Calculation of interlinking completeness for ECLAP took 27.887865781784058s
Reputation | Calculation of the PageRank for ECLAP took 0.021459579467773438s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for ECLAP took 6.723403930664062e-05s
Believability | Calculation of trust value for ECLAP took 1.2636184692382812e-05s
INFO | --- Analysis for eclap took 208.75659227371216s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 4.5299530029296875e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.3934652805328369s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.02121591567993164s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 6.556510925292969e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.8835067749023438e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.3589859008789062e-05s
INFO | --- Analysis for ECNU-GISer took 31.33170747756958s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 8.893013000488281e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 26.11320924758911s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02126026153564453s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 6.031990051269531e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.239776611328125e-05s
INFO | --- Analysis for ecs took 150.1471095085144s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.482269287109375e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 27.366788148880005s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.021927833557128906s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0008409023284912109s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 4.1484832763671875e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 1.1682510375976562e-05s
INFO | --- Analysis for edificios-historicos-zaragoza took 56.17125988006592s
Availability | SPARQL endpoint availability check for Edublogs took 0.00012087821960449219s
Availability | VoID file availability check for Edublogs took 0.0006642341613769531s
Completeness | Calculation of interlinking completeness for Edublogs took 25.137927293777466s
Reputation | Calculation of the PageRank for Edublogs took 0.021332263946533203s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.0001068115234375s
Believability | Calculation of trust value for Edublogs took 1.2874603271484375e-05s
INFO | --- Analysis for edublogs took 106.69088983535767s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.5804767608642578s
Availability | VoID file availability check for education.data.gov.uk took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.34369373321533203s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.023032665252685547s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 3.695487976074219e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.918212890625e-05s
Believability | Calculation of trust value for education.data.gov.uk took 9.5367431640625e-06s
INFO | --- Analysis for education-data-gov-uk took 30.571331024169922s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 391.7788825035095s
Availability | VoID file availability check for Educational programs - SISVU took 0.0012536048889160156s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 29.319441080093384s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.02132248878479004s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 6.413459777832031e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.1444091796875e-05s
INFO | --- Analysis for educationalprograms_sisvu took 1448.819659948349s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 1.171886682510376s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 24.538148880004883s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.02196812629699707s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0008115768432617188s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.553794860839844e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 5.602836608886719e-05s
INFO | --- Analysis for eea took 110.48477292060852s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5217585563659668s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.75335693359375s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.33440208435058594s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.021045684814453125s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 0.0001461505889892578s
Interoperability | Check the re-using of existing vocabs for EEA Reporting Obligations Database took 1.7982523441314697s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 9.298324584960938e-06s
INFO | --- Analysis for eea-rod took 174.93471503257751s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.2051701545715332s
Availability | VoID file availability check for EEA Vocabularies took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.3417072296142578s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.021134614944458008s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.58306884765625e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.2636184692382812e-05s
INFO | --- Analysis for eea-vocabularies took 85.22018361091614s
Availability | SPARQL endpoint availability check for E-Government Ontology took 1.6237492561340332s
Availability | VoID file availability check for E-Government Ontology took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.3831486701965332s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.021351099014282227s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.719329833984375e-05s
Believability | Calculation of trust value for E-Government Ontology took 2.3365020751953125e-05s
INFO | --- Analysis for EGovOntology took 111.73950576782227s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4954657554626465s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0006556510925292969s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 2.289367914199829s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.060804843902588s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5710501670837402s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.003906726837158s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.27890610694885s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 3.9512877464294434s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9354791641235352s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6293115615844727s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2265481948852539s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6569640636444092s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 7.116984128952026s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.20516633987426758s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4187965393066406s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5868246555328369s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.31592774391174316s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3818855285644531s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23492002487182617s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 10.73621129989624s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 7.390975952148438e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.26397156715393066s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.228607177734375s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3159666061401367s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.21304607391357422s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.26685023307800293s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8286604881286621s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23802709579467773s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 6.1404869556427s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.22664928436279297s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.30497121810913086s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.33441615104675293s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8892247676849365s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.030367612838745117s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.02896285057067871s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.20908784866333008s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.01851224899292s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.37348103523254395s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.261312484741211s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3540782928466797s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.116156816482544s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.034905195236206055s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5283355712890625s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5353078842163086s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 2797.5028421878815s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 24.477495670318604s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.02148890495300293s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 6.437301635742188e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1920928955078125e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 8.106231689453125e-06s
INFO | --- Analysis for ei2a took 3123.170304775238s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 0.352886438369751s
Availability | VoID file availability check for EIONET RDF Data took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.3228001594543457s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.022296905517578125s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.0001289844512939453s
Believability | Calculation of trust value for EIONET RDF Data took 9.298324584960938e-06s
INFO | --- Analysis for eionet-rdf took 106.53407192230225s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 9.274482727050781e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.35357165336608887s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.021016359329223633s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.600120544433594e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 7.62939453125e-06s
INFO | --- Analysis for ElgooG_ took 148.42845129966736s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 0.4372265338897705s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.33205509185791016s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.022097110748291016s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 8.416175842285156e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.0728836059570312e-05s
INFO | --- Analysis for elviajero took 85.07880854606628s
Availability | SPARQL endpoint availability check for EMN took 4.673004150390625e-05s
Availability | VoID file availability check for EMN took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for EMN took 24.735396146774292s
Reputation | Calculation of the PageRank for EMN took 0.02112889289855957s
Interlinking | Calculation of Degree of Connection for EMN took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for EMN took 4.291534423828125e-05s
Believability | Calculation of trust value for EMN took 2.0265579223632812e-05s
INFO | --- Analysis for emn took 150.33124542236328s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.38690185546875e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.2902529239654541s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.02108454704284668s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.507469177246094e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 4.76837158203125e-06s
INFO | --- Analysis for enakting-co2emission took 80.50208115577698s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.696846008300781e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 24.711687088012695s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.02180767059326172s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0009174346923828125s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.76837158203125e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for enakting-crime took 52.57721519470215s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.458427429199219e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.31043457984924316s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.02285170555114746s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.363059997558594e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 5.0067901611328125e-06s
INFO | --- Analysis for enakting-energy took 55.48748970031738s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 0.00010561943054199219s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.3401341438293457s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.021992921829223633s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 0.00010347366333007812s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 9.059906005859375e-06s
INFO | --- Analysis for enakting-mortality took 100.09718704223633s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.57763671875e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.29428958892822266s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.02099776268005371s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 4.291534423828125e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 1.4543533325195312e-05s
INFO | --- Analysis for enakting-nhs took 126.3507788181305s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 0.00014734268188476562s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.2989375591278076s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.0209505558013916s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0008041858673095703s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.888938903808594e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 9.059906005859375e-06s
INFO | --- Analysis for enakting-population took 100.38011074066162s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.6628303527832031s
Availability | VoID file availability check for English Heritage Periods List took 4.194552898406982s
Extra | Recovery of all triples for English Heritage Periods List took 0.28234434127807617s
Performance | Total latancy measurement for English Heritage Periods List took 2.4346282482147217s
Amount of data | Number of triples check for English Heritage Periods List took 0.4891090393066406s
Versatility | Languages check for English Heritage Periods List took 0.2743868827819824s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.466296911239624s
Security | Check HTTPS for English Heritage Periods List took 0.21238279342651367s
Interpretability | RDF structures check for English Heritage Periods List took 0.28883934020996094s
Versatility | Serialization formats check for English Heritage Periods List took 0.46923136711120605s
Availability | RDF dump link check for English Heritage Periods List took 0.29808616638183594s
License | MR license check for English Heritage Periods List took 0.37779927253723145s
License | HR license check for English Heritage Periods List took 0.3264462947845459s
Amount of data | Number of property check for English Heritage Periods List took 0.3525881767272949s
Understandability | Number of label check for English Heritage Periods List took 0.4299502372741699s
Understandability | URI regex check for English Heritage Periods List took 0.6314883232116699s
Understandability | Vocabs check for English Heritage Periods List took 0.3480799198150635s
Verifiability | Authors check for English Heritage Periods List took 0.34513139724731445s
Verifiability | Publishers check for English Heritage Periods List took 1.3453900814056396s
Performance | Throughput check for English Heritage Periods List took 12.375593185424805s
Amount of data | Check the number of entities for English Heritage Periods List took 3.147125244140625e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.3825395107269287s
Interlinking | sameAs chians check for English Heritage Periods List took 0.495133638381958s
Interlinking | skos check for English Heritage Periods List took 0.36598730087280273s
Interlinking | skos check for English Heritage Periods List took 0.3768293857574463s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.39188051223754883s
Currency | Creation date check for English Heritage Periods List took 0.6356146335601807s
Currency | Modification date check for English Heritage Periods List took 0.6955561637878418s
Rep.Conc. | URIs length for English Heritage Periods List took 0.6483125686645508s
Interoperability | New vocabularies check for English Heritage Periods List took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.36844539642333984s
Accuracy | Check Functional Property for English Heritage Periods List took 0.3324015140533447s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.3441162109375s
Consistency | Disjoint class check for English Heritage Periods List took 0.32808732986450195s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.4241516590118408s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.7472233772277832s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0005609989166259766s
Security | Sign check for English Heritage Periods List took 0.40495753288269043s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.2835874557495117s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.021350622177124023s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 4.76837158203125e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 7.152557373046875e-07s
Believability | Calculation of trust value for English Heritage Periods List took 1.1920928955078125e-05s
INFO | --- Analysis for english-heritage-periods-list took 146.17011880874634s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.6362299919128418s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0004706382751464844s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 1.2069933414459229s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 1.2580506801605225s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.7255918979644775s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 2.194689989089966s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 1.2978389263153076s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 30.26811671257019s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.12468719482421875s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 1.085054636001587s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.16437339782714844s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 0.5956473350524902s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.8971240520477295s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.26793074607849s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.21967792510986328s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.6203041076660156s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.43936657905578613s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.16017556190490723s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.22086167335510254s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 1.082458734512329s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 12.672815799713135s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 7.152557373046875e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.2153317928314209s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.5308370590209961s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.5220956802368164s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.1993732452392578s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.27883172035217285s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 2.525834083557129s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.9742293357849121s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 3.2915265560150146s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.2748415470123291s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.2578432559967041s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.22075653076171875s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.6309435367584229s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 1.7140471935272217s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 2.7994801998138428s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.6301195621490479s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.0001862049102783203s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.7775990962982178s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.20217347145080566s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.2818300724029541s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02217578887939453s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 4.458427429199219e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.430511474609375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 9.775161743164062e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 386.3913938999176s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.15438175201416016s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0007328987121582031s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 1.0022263526916504s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 1.0137898921966553s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.47149229049682617s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.6020326614379883s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.42499423027038574s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 30.227008819580078s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.18373394012451172s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.1642453670501709s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.13959360122680664s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 52.445313930511475s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.1451125144958496s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.24810218811035s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.20316720008850098s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.15757107734680176s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.3995671272277832s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.21692204475402832s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.20758819580078125s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.24303197860717773s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 11.879755735397339s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 7.152557373046875e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.28394484519958496s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.20275497436523438s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.18961787223815918s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.22928309440612793s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.16400694847106934s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.37223291397094727s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.2134706974029541s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.2369184494018555s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.16362380981445312s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.5808589458465576s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.21671676635742188s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.20127296447753906s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.5175650119781494s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 1.0582234859466553s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.6889548301696777s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.0001647472381591797s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.45931291580200195s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.3236556053161621s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 26.775643587112427s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.021407604217529297s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 4.172325134277344e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Score 2010 took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 9.059906005859375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 468.0771322250366s
Availability | SPARQL endpoint availability check for English WordNet took 9.965896606445312e-05s
Availability | VoID file availability check for English WordNet took 0.00038814544677734375s
Completeness | Calculation of interlinking completeness for English WordNet took 0.296323299407959s
Reputation | Calculation of the PageRank for English WordNet took 0.022270679473876953s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.647804260253906e-05s
Believability | Calculation of trust value for English WordNet took 1.239776611328125e-05s
INFO | --- Analysis for english-wordnet took 101.97679996490479s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.08624863624572754s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.2966313362121582s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.026903390884399414s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0015625953674316406s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 0.00014448165893554688s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.2159347534179688e-05s
INFO | --- Analysis for enipedia took 55.96491765975952s
Availability | SPARQL endpoint availability check for Enslaved.org took 9.107589721679688e-05s
Availability | VoID file availability check for Enslaved.org took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Enslaved.org took 23.60326838493347s
Reputation | Calculation of the PageRank for Enslaved.org took 0.021094560623168945s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.1948089599609375e-05s
Believability | Calculation of trust value for Enslaved.org took 1.1682510375976562e-05s
INFO | --- Analysis for enslaved.org took 122.57061791419983s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.3201732635498047s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.3108382225036621s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.02151656150817871s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0008175373077392578s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 6.29425048828125e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 1.049041748046875e-05s
INFO | --- Analysis for entice-graph took 58.479222774505615s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.649162292480469e-05s
Availability | VoID file availability check for Entrez Gene took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Entrez Gene took 20.918559312820435s
Reputation | Calculation of the PageRank for Entrez Gene took 0.021313190460205078s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 4.100799560546875e-05s
Believability | Calculation of trust value for Entrez Gene took 1.1205673217773438e-05s
INFO | --- Analysis for entrez_gene took 95.63963508605957s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.0322701930999756s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.00038433074951171875s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 28.538844347000122s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.021169662475585938s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 6.0558319091796875e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 7.62939453125e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 157.602933883667s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.30285143852233887s
Availability | VoID file availability check for environment.data.gov.uk took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 26.219906330108643s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.02105712890625s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 5.435943603515625e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 9.298324584960938e-06s
INFO | --- Analysis for environment-data-gov-uk took 111.28966403007507s
Availability | SPARQL endpoint availability check for EARTh took 271.7270276546478s
Availability | VoID file availability check for EARTh took 3.933029890060425s
Completeness | Calculation of interlinking completeness for EARTh took 23.527493238449097s
Reputation | Calculation of the PageRank for EARTh took 0.021743297576904297s
Interlinking | Calculation of Degree of Connection for EARTh took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00012230873107910156s
Interoperability | Check the re-using of existing vocabs for EARTh took 1.1664206981658936s
Believability | Calculation of trust value for EARTh took 1.1920928955078125e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 858.3638453483582s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.521425724029541s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0003497600555419922s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 101.68386840820312s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.9865715503692627s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 9.387717008590698s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 14.326191663742065s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.20244431495667s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.2960896492004395s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.302868127822876s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 13.381745338439941s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.3291950225830078s
License | MR license check for Micka (EO metadata) @PSNC took 0.7487201690673828s
License | HR license check for Micka (EO metadata) @PSNC took 300.2126245498657s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.19492220878601074s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 2.5065178871154785s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 0.9554657936096191s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.515437126159668s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.2058429718017578s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.2621941566467285s
Performance | Throughput check for Micka (EO metadata) @PSNC took 11.653228044509888s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 8.535385131835938e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.20186090469360352s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.20439791679382324s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.5092003345489502s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4127945899963379s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 6.724074602127075s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.4611492156982422s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.2524726390838623s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 146.73541712760925s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.19999957084655762s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.5973432064056396s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.47031331062316895s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 36.537635803222656s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.6849710941314697s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.677473783493042s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.19328069686889648s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 86.57964134216309s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.508577108383179s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 31.030279874801636s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.5089354515075684s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 87.7708330154419s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.7816343307495117s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.5388400554656982s
Security | Sign check for Micka (EO metadata) @PSNC took 1.5514757633209229s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 2.1908693313598633s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 29.946895122528076s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.02131795883178711s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 5.626678466796875e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 1.1444091796875e-05s
INFO | --- Analysis for EO_metadata took 2317.1160929203033s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 9.989738464355469e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.35308241844177246s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.021414756774902344s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.790855407714844e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 7.867813110351562e-06s
INFO | --- Analysis for EOKP-Datasets took 78.793541431427s
Availability | SPARQL endpoint availability check for EPA-CDR took 5.435943603515625e-05s
Availability | VoID file availability check for EPA-CDR took 0.0007684230804443359s
Completeness | Calculation of interlinking completeness for EPA-CDR took 24.81652808189392s
Reputation | Calculation of the PageRank for EPA-CDR took 0.021033048629760742s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 4.458427429199219e-05s
Believability | Calculation of trust value for EPA-CDR took 2.1219253540039062e-05s
INFO | --- Analysis for epa-cdr took 165.15744638442993s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.410743713378906e-05s
Availability | VoID file availability check for EPA-FRS took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.31644344329833984s
Reputation | Calculation of the PageRank for EPA-FRS took 0.021435260772705078s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.700920104980469e-05s
Believability | Calculation of trust value for EPA-FRS took 9.5367431640625e-06s
INFO | --- Analysis for epa-frs took 118.74793910980225s
Availability | SPARQL endpoint availability check for EPA-RCRA took 9.274482727050781e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.32389116287231445s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.021465778350830078s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 4.673004150390625e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.0067901611328125e-06s
INFO | --- Analysis for epa-rcra took 99.75106644630432s
Availability | SPARQL endpoint availability check for EPA-SRS took 9.131431579589844e-05s
Availability | VoID file availability check for EPA-SRS took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for EPA-SRS took 26.78625464439392s
Reputation | Calculation of the PageRank for EPA-SRS took 0.021338462829589844s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.796287536621094e-05s
Believability | Calculation of trust value for EPA-SRS took 9.298324584960938e-06s
INFO | --- Analysis for epa-srs took 175.68213605880737s
Availability | SPARQL endpoint availability check for EPA-TRI took 5.0067901611328125e-05s
Availability | VoID file availability check for EPA-TRI took 0.0007605552673339844s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.32211947441101074s
Reputation | Calculation of the PageRank for EPA-TRI took 0.02164626121520996s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 4.076957702636719e-05s
Believability | Calculation of trust value for EPA-TRI took 9.298324584960938e-06s
INFO | --- Analysis for epa-tri took 111.97108268737793s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.036783456802368164s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.28993773460388184s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020991086959838867s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.0001437664031982422s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 52.452478885650635s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.48061060905456543s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 23.785155057907104s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.02107691764831543s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.535385131835938e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 1.2159347534179688e-05s
INFO | --- Analysis for eprtr took 133.11245226860046s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.49805283546447754s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0006742477416992188s
Extra | Recovery of all triples for Railway Infrastructure KG took 57.71307444572449s
Performance | Total latancy measurement for Railway Infrastructure KG took 1.1112048625946045s
Amount of data | Number of triples check for Railway Infrastructure KG took 0.22788071632385254s
Interoperability | New terms check for Railway Infrastructure KG took 1.7630045413970947s
Versatility | Languages check for Railway Infrastructure KG took 79.59149479866028s
Interpretability | Number of blank nodes check for Railway Infrastructure KG took 0.26195764541625977s
Interpretability | RDF structures check for Railway Infrastructure KG took 0.3799104690551758s
Versatility | Serialization formats check for Railway Infrastructure KG took 0.2973175048828125s
Availability | RDF dump link check for Railway Infrastructure KG took 0.22024989128112793s
License | MR license check for Railway Infrastructure KG took 0.343001127243042s
License | HR license check for Railway Infrastructure KG took 65.24043679237366s
Amount of data | Number of property check for Railway Infrastructure KG took 0.2606546878814697s
Understandability | Number of label check for Railway Infrastructure KG took 0.4833240509033203s
Understandability | URI regex check for Railway Infrastructure KG took 0.4527108669281006s
Understandability | Vocabs check for Railway Infrastructure KG took 0.284808874130249s
Verifiability | Authors check for Railway Infrastructure KG took 0.30673670768737793s
Verifiability | Publishers check for Railway Infrastructure KG took 0.23478960990905762s
Performance | Throughput check for Railway Infrastructure KG took 11.3016676902771s
Verifiability | Contribs. check for Railway Infrastructure KG took 0.26462554931640625s
Interlinking | sameAs chians check for Railway Infrastructure KG took 0.22956156730651855s
Interlinking | skos check for Railway Infrastructure KG took 0.2643463611602783s
Interlinking | skos check for Railway Infrastructure KG took 0.2440962791442871s
Timeliness | dataset update frequency check for Railway Infrastructure KG took 0.2427225112915039s
Currency | Creation date check for Railway Infrastructure KG took 0.49955034255981445s
Currency | Modification date check for Railway Infrastructure KG took 0.21477556228637695s
Rep.Conc. | URIs length for Railway Infrastructure KG took 23.26526689529419s
Interoperability | New vocabularies check for Railway Infrastructure KG took 6.765466213226318s
Consistency | Deprecated classes/propertiers check for Railway Infrastructure KG took 0.22066855430603027s
Accuracy | Check Functional Property for Railway Infrastructure KG took 0.23854684829711914s
Accuracy | Check Inverse Functional Property for Railway Infrastructure KG took 0.256472110748291s
Accuracy | Check Empty annotation labels for Railway Infrastructure KG took 14.511709213256836s
Accuracy | Check White space in annotation for Railway Infrastructure KG took 2.5978028774261475s
Accuracy | Check Datatype consistency for Railway Infrastructure KG took 2.69211483001709s
Consistency | Disjoint class check for Railway Infrastructure KG took 0.2571859359741211s
Consistency | Check Misplaced properties for Railway Infrastructure KG took 1.7506303787231445s
Consistency | Misplaced classes for Railway Infrastructure KG took 8.598721027374268s
Consistency | Check Ontology hijacking for Railway Infrastructure KG took 18.884129285812378s
Consistency | Check Invalid usage of undefined classes for Railway Infrastructure KG took 1.6049778461456299s
Consistency | Check Invalid usage of undefined properties for Railway Infrastructure KG took 2.9467413425445557s
Conciseness | Check Extensional conciseness for Railway Infrastructure KG took 2.893648386001587s
Conciseness | Check Intensional conciseness for Railway Infrastructure KG took 0.35915493965148926s
Security | Sign check for Railway Infrastructure KG took 0.3031158447265625s
Availability | Check URIs Dereferenciability for Railway Infrastructure KG took 2361.1753010749817s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.36038947105407715s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.022790908813476562s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 7.462501525878906e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0008165836334228516s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 4.76837158203125e-05s
Interoperability | Check the re-using of existing vocabs for Railway Infrastructure KG took 5.134926080703735s
Believability | Calculation of trust value for Railway Infrastructure KG took 1.1444091796875e-05s
INFO | --- Analysis for ERAKG took 2874.270310163498s
Availability | SPARQL endpoint availability check for reg took 4.982948303222656e-05s
Availability | VoID file availability check for reg took 0.0003104209899902344s
Completeness | Calculation of interlinking completeness for reg took 0.2967250347137451s
Reputation | Calculation of the PageRank for reg took 0.022225141525268555s
Interlinking | Calculation of Degree of Connection for reg took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for reg took 0.0008528232574462891s
Interlinking | Calculation of Clustering coefficient for reg took 2.288818359375e-05s
Believability | Calculation of trust value for reg took 7.3909759521484375e-06s
INFO | --- Analysis for erg took 78.66104221343994s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.15305113792419434s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.3476986885070801s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.021151304244995117s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.4809112548828125e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 8.58306884765625e-06s
INFO | --- Analysis for es-msssi-drug-prices took 81.07526230812073s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 9.131431579589844e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.315371036529541s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02276444435119629s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 9.5367431640625e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 9.298324584960938e-06s
INFO | --- Analysis for esd-standards took 110.40487027168274s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.410743713378906e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.29572033882141113s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.0222930908203125s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 8.153915405273438e-05s
Believability | Calculation of trust value for ESD-Toolkit took 4.5299530029296875e-06s
INFO | --- Analysis for esd-toolkit took 102.56195998191833s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.506111145019531e-05s
Availability | VoID file availability check for Dataset Esis took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.3293590545654297s
Reputation | Calculation of the PageRank for Dataset Esis took 0.021072864532470703s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0008392333984375s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.218650817871094e-05s
Believability | Calculation of trust value for Dataset Esis took 1.1205673217773438e-05s
INFO | --- Analysis for esislearning took 57.254263401031494s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 5.14984130859375e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 25.82679796218872s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.021606922149658203s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0008502006530761719s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 4.291534423828125e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 1.2159347534179688e-05s
INFO | --- Analysis for ESV took 198.7071614265442s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.6199002265930176s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0008149147033691406s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.3272249698638916s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.021307945251464844s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 5.173683166503906e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 159.52670812606812s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 5.6032702922821045s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.34355783462524414s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.0215299129486084s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0008335113525390625s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 8.344650268554688e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 8.106231689453125e-06s
INFO | --- Analysis for eu-agencies-bodies took 86.08994460105896s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 8.988380432128906e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 21.130504608154297s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.021005630493164062s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 8.58306884765625e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 5.9604644775390625e-06s
INFO | --- Analysis for eu-institutions took 100.51022148132324s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.121932029724121s
Availability | VoID file availability check for EU Parliament Media Library took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 26.640286684036255s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02129650115966797s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.719329833984375e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 5.245208740234375e-06s
INFO | --- Analysis for eu-parliament-media took 62.57115292549133s
Availability | SPARQL endpoint availability check for EU Who Is Who took 1.002758502960205s
Availability | VoID file availability check for EU Who Is Who took 0.0007469654083251953s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.3149404525756836s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.021259546279907227s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 4.1484832763671875e-05s
Believability | Calculation of trust value for EU Who Is Who took 9.298324584960938e-06s
INFO | --- Analysis for eu-who-is-who took 80.82064080238342s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 1.0637941360473633s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.311845064163208s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.021367788314819336s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0008223056793212891s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.887580871582031e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for eumida-linked-data took 87.02164554595947s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.36719655990600586s
Availability | VoID file availability check for European Nature Information System took 0.5080776214599609s
Completeness | Calculation of interlinking completeness for European Nature Information System took 27.050628662109375s
Reputation | Calculation of the PageRank for European Nature Information System took 0.0217592716217041s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00011157989501953125s
Interoperability | Check the re-using of existing vocabs for European Nature Information System took 3.735067844390869s
Believability | Calculation of trust value for European Nature Information System took 1.3589859008789062e-05s
INFO | --- Analysis for eunis took 84.13697457313538s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 5.370424747467041s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0007677078247070312s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 23.618370532989502s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.021401166915893555s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 9.465217590332031e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 1.1682510375976562e-05s
INFO | --- Analysis for eur-lex-rdf took 116.28816342353821s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 0.9742636680603027s
Availability | VoID file availability check for Standard Eurobarometer took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 22.526209592819214s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.0211794376373291s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0008995532989501953s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 0.00010251998901367188s
Believability | Calculation of trust value for Standard Eurobarometer took 9.298324584960938e-06s
INFO | --- Analysis for eurobarometer-standard took 107.59119749069214s
Availability | SPARQL endpoint availability check for European Election Results took 1.065028429031372s
Availability | VoID file availability check for European Election Results took 0.0008208751678466797s
Completeness | Calculation of interlinking completeness for European Election Results took 23.30979347229004s
Reputation | Calculation of the PageRank for European Election Results took 0.021127939224243164s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for European Election Results took 4.887580871582031e-05s
Believability | Calculation of trust value for European Election Results took 9.5367431640625e-06s
INFO | --- Analysis for european-election-results took 57.695448875427246s
Availability | SPARQL endpoint availability check for EPO patents took 0.39104723930358887s
Availability | VoID file availability check for EPO patents took 0.0006074905395507812s
Extra | Recovery of all triples for EPO patents took 28.550411224365234s
Performance | Total latancy measurement for EPO patents took 1.0701181888580322s
Amount of data | Number of triples check for EPO patents took 90.21999621391296s
Versatility | Languages check for EPO patents took 100.28656888008118s
Interpretability | Number of blank nodes check for EPO patents took 100.2857494354248s
Interpretability | RDF structures check for EPO patents took 29.507448196411133s
Versatility | Serialization formats check for EPO patents took 0.18923306465148926s
Availability | RDF dump link check for EPO patents took 0.29537487030029297s
License | MR license check for EPO patents took 0.23740339279174805s
License | HR license check for EPO patents took 90.20367646217346s
Amount of data | Number of property check for EPO patents took 0.161651611328125s
Understandability | Number of label check for EPO patents took 90.23094987869263s
Understandability | URI regex check for EPO patents took 0.4603614807128906s
Understandability | Vocabs check for EPO patents took 0.19727849960327148s
Verifiability | Authors check for EPO patents took 0.30224108695983887s
Verifiability | Publishers check for EPO patents took 0.29123806953430176s
Performance | Throughput check for EPO patents took 11.22411298751831s
Amount of data | Check the number of entities for EPO patents took 7.963180541992188e-05s
Verifiability | Contribs. check for EPO patents took 0.19308233261108398s
Interlinking | sameAs chians check for EPO patents took 0.173295259475708s
Interlinking | skos check for EPO patents took 0.16052865982055664s
Interlinking | skos check for EPO patents took 0.16395235061645508s
Timeliness | dataset update frequency check for EPO patents took 0.1894228458404541s
Currency | Creation date check for EPO patents took 0.3528473377227783s
Currency | Modification date check for EPO patents took 0.35860776901245117s
Rep.Conc. | URIs length for EPO patents took 131.71802139282227s
Interoperability | New vocabularies check for EPO patents took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 20.025992155075073s
Accuracy | Check Empty annotation labels for EPO patents took 15.477220296859741s
Accuracy | Check White space in annotation for EPO patents took 3.012648344039917s
Accuracy | Check Datatype consistency for EPO patents took 4.947674989700317s
Consistency | Disjoint class check for EPO patents took 0.19897150993347168s
Consistency | Check Misplaced properties for EPO patents took 100.44664335250854s
Consistency | Check Ontology hijacking for EPO patents took 38.38483810424805s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.7657320499420166s
Consistency | Check Invalid usage of undefined properties for EPO patents took 101.73621344566345s
Conciseness | Check Extensional conciseness for EPO patents took 2.858726739883423s
Conciseness | Check Intensional conciseness for EPO patents took 15.79087233543396s
Security | Sign check for EPO patents took 0.23508763313293457s
Availability | Check URIs Dereferenciability for EPO patents took 2.10632061958313s
Completeness | Calculation of interlinking completeness for EPO patents took 0.42358851432800293s
Reputation | Calculation of the PageRank for EPO patents took 0.021982669830322266s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for EPO patents took 5.2928924560546875e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 2.384185791015625e-06s
Believability | Calculation of trust value for EPO patents took 7.3909759521484375e-06s
INFO | --- Analysis for European_Patent_Information took 1381.8066620826721s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 9.179115295410156e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.2156813144683838s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.36633825302124023s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.021170616149902344s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.560585021972656e-05s
Interoperability | Check the re-using of existing vocabs for Europeana Linked Open Data V1.0 took 11.171838283538818s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 2.384185791015625e-05s
INFO | --- Analysis for europeana-lod-v1 took 162.3731336593628s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.4189939498901367s
Availability | VoID file availability check for Europeana SPARQL took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 23.7023983001709s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.025664806365966797s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.001253366470336914s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 7.033348083496094e-05s
Believability | Calculation of trust value for Europeana SPARQL took 1.1682510375976562e-05s
INFO | --- Analysis for europeana-sparql took 151.36471796035767s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.10833239555358887s
Availability | VoID file availability check for EuroSentiment took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for EuroSentiment took 24.32430124282837s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02121424674987793s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 4.124641418457031e-05s
Believability | Calculation of trust value for EuroSentiment took 1.239776611328125e-05s
INFO | --- Analysis for eurosentiment took 153.22071170806885s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 9.226799011230469e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0007369518280029297s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.37935709953308105s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.021449804306030273s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 0.00011682510375976562s
Believability | Calculation of trust value for Eurostat RDF datasets took 5.0067901611328125e-06s
INFO | --- Analysis for eurostat-rdf took 104.88187003135681s
Availability | SPARQL endpoint availability check for EuroVoc took 0.18739938735961914s
Availability | VoID file availability check for EuroVoc took 0.0007648468017578125s
Extra | Recovery of all triples for EuroVoc took 187.31992840766907s
Performance | Total latancy measurement for EuroVoc took 0.609367847442627s
Amount of data | Number of triples check for EuroVoc took 55.957733392715454s
Interoperability | New terms check for EuroVoc took 55.83831596374512s
Versatility | Languages check for EuroVoc took 300.13405561447144s
Interpretability | Number of blank nodes check for EuroVoc took 15.415660381317139s
Security | Check HTTPS for EuroVoc took 0.343519926071167s
Interpretability | RDF structures check for EuroVoc took 0.5064384937286377s
Versatility | Serialization formats check for EuroVoc took 3.2649683952331543s
Availability | RDF dump link check for EuroVoc took 0.3096351623535156s
License | MR license check for EuroVoc took 0.5316472053527832s
License | HR license check for EuroVoc took 300.0518801212311s
Amount of data | Number of property check for EuroVoc took 0.2728109359741211s
Understandability | Number of label check for EuroVoc took 1.848733901977539s
Understandability | URI regex check for EuroVoc took 0.5018632411956787s
Understandability | Vocabs check for EuroVoc took 0.11421751976013184s
Verifiability | Authors check for EuroVoc took 0.20227766036987305s
Verifiability | Publishers check for EuroVoc took 0.3324108123779297s
Performance | Throughput check for EuroVoc took 11.041151285171509s
Amount of data | Check the number of entities for EuroVoc took 7.82012939453125e-05s
Verifiability | Contribs. check for EuroVoc took 0.10779833793640137s
Interlinking | sameAs chians check for EuroVoc took 7.341473579406738s
Interlinking | skos check for EuroVoc took 0.361910343170166s
Interlinking | skos check for EuroVoc took 0.1327500343322754s
Timeliness | dataset update frequency check for EuroVoc took 0.30811643600463867s
Currency | Creation date check for EuroVoc took 0.6252210140228271s
Currency | Modification date check for EuroVoc took 0.26511168479919434s
Rep.Conc. | URIs length for EuroVoc took 414.65446066856384s
Interoperability | New vocabularies check for EuroVoc took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.21364617347717285s
Accuracy | Check Functional Property for EuroVoc took 0.21893620491027832s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.17479276657104492s
Accuracy | Check Empty annotation labels for EuroVoc took 40.98893713951111s
Accuracy | Check White space in annotation for EuroVoc took 3.094147205352783s
Accuracy | Check Datatype consistency for EuroVoc took 2.721423625946045s
Consistency | Disjoint class check for EuroVoc took 0.15575337409973145s
Consistency | Check Misplaced properties for EuroVoc took 300.455854177475s
Consistency | Misplaced classes for EuroVoc took 8.740665912628174s
Consistency | Check Ontology hijacking for EuroVoc took 38.733498096466064s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.659850835800171s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.6514518260956s
Conciseness | Check Extensional conciseness for EuroVoc took 3.070014715194702s
Conciseness | Check Intensional conciseness for EuroVoc took 0.3465437889099121s
Security | Sign check for EuroVoc took 0.2744879722595215s
Availability | Check URIs Dereferenciability for EuroVoc took 11.233326196670532s
Completeness | Calculation of interlinking completeness for EuroVoc took 0.8072946071624756s
Reputation | Calculation of the PageRank for EuroVoc took 0.02156972885131836s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 9.036064147949219e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 4.76837158203125e-06s
Believability | Calculation of trust value for EuroVoc took 8.106231689453125e-06s
INFO | --- Analysis for eurovoc took 14988.63618516922s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 0.00010895729064941406s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0007278919219970703s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 19.225696563720703s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.02139592170715332s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 6.103515625e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 9.059906005859375e-06s
INFO | --- Analysis for euskadi-farmacias took 134.2060296535492s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.7317855358123779s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.2924163341522217s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.02113628387451172s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.62396240234375e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 1.621246337890625e-05s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 67.45994544029236s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.48305821418762207s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0007479190826416016s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 27.994252920150757s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.021603107452392578s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 9.083747863769531e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 1.5020370483398438e-05s
INFO | --- Analysis for eutc-productions took 59.79279351234436s
Availability | SPARQL endpoint availability check for EventMedia took 0.38732004165649414s
Availability | VoID file availability check for EventMedia took 0.0007178783416748047s
Completeness | Calculation of interlinking completeness for EventMedia took 19.53537154197693s
Reputation | Calculation of the PageRank for EventMedia took 0.02306532859802246s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0010561943054199219s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00014138221740722656s
Believability | Calculation of trust value for EventMedia took 8.106231689453125e-06s
INFO | --- Analysis for event-media took 171.45042395591736s
Availability | SPARQL endpoint availability check for EventKG took 9.512901306152344e-05s
Availability | VoID file availability check for EventKG took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for EventKG took 0.27791714668273926s
Reputation | Calculation of the PageRank for EventKG took 0.021867752075195312s
Interlinking | Calculation of Degree of Connection for EventKG took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for EventKG took 9.989738464355469e-05s
Believability | Calculation of trust value for EventKG took 1.239776611328125e-05s
INFO | --- Analysis for eventkg took 190.24511218070984s
Availability | SPARQL endpoint availability check for Eventseer took 1.6456563472747803s
Availability | VoID file availability check for Eventseer took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Eventseer took 17.308908224105835s
Reputation | Calculation of the PageRank for Eventseer took 0.021358013153076172s
Interlinking | Calculation of Degree of Connection for Eventseer took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Eventseer took 5.459785461425781e-05s
Believability | Calculation of trust value for Eventseer took 1.3113021850585938e-05s
INFO | --- Analysis for eventseer took 130.8732147216797s
Availability | SPARQL endpoint availability check for Face Link took 9.250640869140625e-05s
Availability | VoID file availability check for Face Link took 0.0003407001495361328s
Completeness | Calculation of interlinking completeness for Face Link took 17.57949709892273s
Reputation | Calculation of the PageRank for Face Link took 0.021364450454711914s
Interlinking | Calculation of Degree of Connection for Face Link took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Face Link took 5.6743621826171875e-05s
Believability | Calculation of trust value for Face Link took 1.1682510375976562e-05s
INFO | --- Analysis for Face_Link took 143.30234956741333s
Availability | SPARQL endpoint availability check for Fact Forge took 0.3428342342376709s
Availability | VoID file availability check for Fact Forge took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Fact Forge took 17.37650752067566s
Reputation | Calculation of the PageRank for Fact Forge took 0.026830673217773438s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.0010190010070800781s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 3.981590270996094e-05s
Believability | Calculation of trust value for Fact Forge took 1.3113021850585938e-05s
INFO | --- Analysis for fact-forge took 99.75010108947754s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5762410163879395s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0005428791046142578s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 115.58726620674133s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9456794261932373s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.219936847686768s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 14.176166296005249s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.2493782043457s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.504408836364746s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.31897902488708496s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 12.126501321792603s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3869445323944092s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9148004055023193s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.22925662994385s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2012166976928711s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.9732184410095215s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.2218046188354492s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.6510396003723145s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.1905651092529297s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.24435830116271973s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.44940733909607s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.724761962890625e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18282866477966309s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18764495849609375s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.508042573928833s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4894740581512451s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.87158465385437s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5049881935119629s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.24919915199279785s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 165.15755772590637s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.20471596717834473s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.40364503860473633s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4304969310760498s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 36.50653696060181s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.7091877460479736s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.66831636428833s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21142244338989258s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 85.92638874053955s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.484153985977173s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 42.40984511375427s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.5043692588806152s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 87.06548929214478s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.7908501625061035s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.6211917400360107s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3336172103881836s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.272979021072388s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 19.650938034057617s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.021582841873168945s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.86102294921875e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.58306884765625e-06s
INFO | --- Analysis for FADN_(2019) took 2683.2562079429626s
Availability | SPARQL endpoint availability check for FAMEData took 4.506111145019531e-05s
Availability | VoID file availability check for FAMEData took 0.0008533000946044922s
Completeness | Calculation of interlinking completeness for FAMEData took 25.660064697265625s
Reputation | Calculation of the PageRank for FAMEData took 0.02175736427307129s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for FAMEData took 4.076957702636719e-05s
Believability | Calculation of trust value for FAMEData took 1.1205673217773438e-05s
INFO | --- Analysis for famedata took 139.8356556892395s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 0.0001800060272216797s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 27.00378155708313s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.02356886863708496s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.00010919570922851562s
Believability | Calculation of trust value for FAO geopolitical ontology took 8.821487426757812e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 157.62420773506165s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.12482547760009766s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 19.34050703048706s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.021450519561767578s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00012254714965820312s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for fao-linked-data took 155.25190591812134s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 9.632110595703125e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 25.783549308776855s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.021347999572753906s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.001959085464477539s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 4.4345855712890625e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for FAO_species took 107.13868117332458s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.68615484237671s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 19.130839824676514s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.021114587783813477s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 5.221366882324219e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 8.821487426757812e-06s
INFO | --- Analysis for farmbio-chembl took 195.646803855896s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.863739013671875e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.31269121170043945s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.02303004264831543s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 4.220008850097656e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.4781951904296875e-05s
INFO | --- Analysis for fatimazahra took 79.98998069763184s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.792213439941406e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.3234238624572754s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.021721363067626953s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0010879039764404297s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 3.9577484130859375e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.1920928955078125e-05s
INFO | --- Analysis for FHIR_STU3 took 160.29856610298157s
Availability | SPARQL endpoint availability check for FiESTA took 4.553794860839844e-05s
Availability | VoID file availability check for FiESTA took 0.0008511543273925781s
Completeness | Calculation of interlinking completeness for FiESTA took 21.439852952957153s
Reputation | Calculation of the PageRank for FiESTA took 0.022738933563232422s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for FiESTA took 5.125999450683594e-05s
Believability | Calculation of trust value for FiESTA took 1.1920928955078125e-05s
INFO | --- Analysis for fiesta took 152.61210346221924s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 5.221366882324219e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.3000049591064453s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0215761661529541s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.504753112792969e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 7.62939453125e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 88.46116971969604s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 0.00011467933654785156s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 19.385236263275146s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.02170586585998535s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 8.416175842285156e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 9.775161743164062e-06s
INFO | --- Analysis for finnish-municipalities took 94.23310160636902s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.22421836853027344s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0005381107330322266s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 106.80726909637451s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 0.9843297004699707s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 9.596187353134155s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 14.591777563095093s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.18242025375366s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 2.5302765369415283s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.24141597747802734s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 9.111972332000732s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.3813176155090332s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.9226839542388916s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.23665046691895s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.20802760124206543s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 3.0445590019226074s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 1.2557859420776367s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.6960694789886475s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.1961994171142578s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.23391962051391602s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 11.357838153839111s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 3.147125244140625e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.20784831047058105s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.1881091594696045s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4929695129394531s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4398033618927002s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 6.156440496444702s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.561284065246582s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.2461404800415039s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 165.63483452796936s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.21878504753112793s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.5640056133270264s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.5005753040313721s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 39.12233924865723s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.6965091228485107s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.6926791667938232s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.19837307929992676s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 88.25427556037903s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.39915919303894s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 33.73483324050903s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.5214755535125732s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 89.0879499912262s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.7590184211730957s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.5489835739135742s
Security | Sign check for Norway fishery stocks dataset @PSNC took 1.392601728439331s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 10.10498332977295s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.7553386688232422s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.022289276123046875s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 4.696846008300781e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.1444091796875e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 2309.6516592502594s
Availability | SPARQL endpoint availability check for Fishes of Texas took 9.250640869140625e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0008876323699951172s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 19.85438823699951s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.021548748016357422s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 0.00010585784912109375s
Believability | Calculation of trust value for Fishes of Texas took 1.1682510375976562e-05s
INFO | --- Analysis for fishes-of-texas took 231.96836709976196s
Availability | SPARQL endpoint availability check for flickr? wrappr took 9.083747863769531e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 17.823811769485474s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.022799253463745117s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 0.0001010894775390625s
Believability | Calculation of trust value for flickr? wrappr took 1.1920928955078125e-05s
INFO | --- Analysis for flickr-wrappr took 79.09226727485657s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.38690185546875e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 24.53487253189087s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.021201133728027344s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.409385681152344e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.1682510375976562e-05s
INFO | --- Analysis for FLUS took 115.07432770729065s
Availability | SPARQL endpoint availability check for Flybase took 1.2620937824249268s
Availability | VoID file availability check for Flybase took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for Flybase took 0.290698766708374s
Reputation | Calculation of the PageRank for Flybase took 0.02266216278076172s
Interlinking | Calculation of Degree of Connection for Flybase took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0008733272552490234s
Interlinking | Calculation of Clustering coefficient for Flybase took 5.650520324707031e-05s
Believability | Calculation of trust value for Flybase took 1.2159347534179688e-05s
INFO | --- Analysis for flybase took 161.5024082660675s
Availability | SPARQL endpoint availability check for Flyted took 1.1509292125701904s
Availability | VoID file availability check for Flyted took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for Flyted took 19.189043283462524s
Reputation | Calculation of the PageRank for Flyted took 0.030028581619262695s
Interlinking | Calculation of Degree of Connection for Flyted took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Flyted took 4.291534423828125e-05s
Believability | Calculation of trust value for Flyted took 1.2874603271484375e-05s
INFO | --- Analysis for flyted took 136.06072735786438s
Availability | SPARQL endpoint availability check for Foodista took 5.747823715209961s
Availability | VoID file availability check for Foodista took 0.0007674694061279297s
Completeness | Calculation of interlinking completeness for Foodista took 19.61246109008789s
Reputation | Calculation of the PageRank for Foodista took 0.021404027938842773s
Interlinking | Calculation of Degree of Connection for Foodista took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Foodista took 4.8160552978515625e-05s
Believability | Calculation of trust value for Foodista took 1.239776611328125e-05s
INFO | --- Analysis for foodista took 141.23449635505676s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.06579923629760742s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.3123595714569092s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.021071195602416992s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.510185241699219e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1444091796875e-05s
INFO | --- Analysis for foodpedia took 61.600287675857544s
Availability | SPARQL endpoint availability check for FORGE Course information took 0.0003304481506347656s
Availability | VoID file availability check for FORGE Course information took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.34794187545776367s
Reputation | Calculation of the PageRank for FORGE Course information took 0.022394657135009766s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.000843048095703125s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 4.291534423828125e-05s
Believability | Calculation of trust value for FORGE Course information took 1.8835067749023438e-05s
INFO | --- Analysis for forge-course-information took 114.74731206893921s
Availability | SPARQL endpoint availability check for FrameBase schema took 5.412101745605469e-05s
Availability | VoID file availability check for FrameBase schema took 0.0008559226989746094s
Completeness | Calculation of interlinking completeness for FrameBase schema took 27.31502628326416s
Reputation | Calculation of the PageRank for FrameBase schema took 0.021994590759277344s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 5.9604644775390625e-05s
Believability | Calculation of trust value for FrameBase schema took 8.106231689453125e-06s
INFO | --- Analysis for framebase-schema took 137.492431640625s
Availability | SPARQL endpoint availability check for Framester took 0.7200262546539307s
Availability | VoID file availability check for Framester took 0.0006651878356933594s
Extra | Recovery of all triples for Framester took 60.57201313972473s
Performance | Total latancy measurement for Framester took 2.0935518741607666s
Amount of data | Number of triples check for Framester took 50.745293855667114s
Versatility | Languages check for Framester took 60.541303396224976s
Interpretability | Number of blank nodes check for Framester took 0.5669009685516357s
Interpretability | RDF structures check for Framester took 1.2839431762695312s
Versatility | Serialization formats check for Framester took 1.390575885772705s
Availability | RDF dump link check for Framester took 4.982838153839111s
License | MR license check for Framester took 2.1361989974975586s
License | HR license check for Framester took 60.51441287994385s
Amount of data | Number of property check for Framester took 0.4506556987762451s
Understandability | Number of label check for Framester took 13.229561567306519s
Understandability | URI regex check for Framester took 1.5639581680297852s
Understandability | Vocabs check for Framester took 0.6569280624389648s
Verifiability | Authors check for Framester took 0.884699821472168s
Verifiability | Publishers check for Framester took 0.6563022136688232s
Performance | Throughput check for Framester took 12.346307516098022s
Amount of data | Check the number of entities for Framester took 9.965896606445312e-05s
Verifiability | Contribs. check for Framester took 0.912259578704834s
Interlinking | sameAs chians check for Framester took 0.6333222389221191s
Interlinking | skos check for Framester took 1.768721103668213s
Interlinking | skos check for Framester took 0.4434854984283447s
Timeliness | dataset update frequency check for Framester took 0.42676520347595215s
Currency | Creation date check for Framester took 1.2646915912628174s
Currency | Modification date check for Framester took 1.011063575744629s
Rep.Conc. | URIs length for Framester took 121.01117014884949s
Interoperability | New vocabularies check for Framester took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Framester took 0.43456435203552246s
Accuracy | Check Functional Property for Framester took 0.5808501243591309s
Accuracy | Check Inverse Functional Property for Framester took 0.5412609577178955s
Consistency | Disjoint class check for Framester took 0.513709306716919s
Consistency | Check Misplaced properties for Framester took 127.30442714691162s
Consistency | Misplaced classes for Framester took 0.6107571125030518s
Consistency | Check Ontology hijacking for Framester took 60.55246448516846s
Consistency | Check Invalid usage of undefined properties for Framester took 61.890843629837036s
Conciseness | Check Extensional conciseness for Framester took 0.00017118453979492188s
Conciseness | Check Intensional conciseness for Framester took 0.635932445526123s
Security | Sign check for Framester took 1.612525224685669s
Completeness | Calculation of interlinking completeness for Framester took 0.36823177337646484s
Reputation | Calculation of the PageRank for Framester took 0.022055864334106445s
Interlinking | Calculation of Degree of Connection for Framester took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Framester took 0.00011920928955078125s
Interoperability | Check the re-using of existing vocabs for Framester took 1.6689300537109375e-06s
Believability | Calculation of trust value for Framester took 8.58306884765625e-06s
INFO | --- Analysis for framester took 1261.118290901184s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.11280632019042969s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.27791285514831543s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.02581048011779785s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 9.989738464355469e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for frb-linked-data took 77.41666173934937s
Availability | SPARQL endpoint availability check for 1989shack Inc. E-Commerce  took 0.00011515617370605469s
Availability | VoID file availability check for 1989shack Inc. E-Commerce  took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for 1989shack Inc. E-Commerce  took 18.75815224647522s
Reputation | Calculation of the PageRank for 1989shack Inc. E-Commerce  took 0.021337270736694336s
Interlinking | Calculation of Degree of Connection for 1989shack Inc. E-Commerce  took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for 1989shack Inc. E-Commerce  took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for 1989shack Inc. E-Commerce  took 0.0002815723419189453s
Believability | Calculation of trust value for 1989shack Inc. E-Commerce  took 1.1682510375976562e-05s
INFO | --- Analysis for freebase took 137.22162580490112s
Availability | SPARQL endpoint availability check for Freeyork took 9.417533874511719e-05s
Availability | VoID file availability check for Freeyork took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Freeyork took 0.28909850120544434s
Reputation | Calculation of the PageRank for Freeyork took 0.022060871124267578s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010776519775390625s
Believability | Calculation of trust value for Freeyork took 1.049041748046875e-05s
INFO | --- Analysis for freeyork-org took 28.72386074066162s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 1.0242393016815186s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.3006002902984619s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.02185654640197754s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.772445678710938e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 1.0728836059570312e-05s
INFO | --- Analysis for fu-berlin-cordis took 147.67138242721558s
Availability | SPARQL endpoint availability check for DailyMed took 0.6633007526397705s
Availability | VoID file availability check for DailyMed took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for DailyMed took 0.31357622146606445s
Reputation | Calculation of the PageRank for DailyMed took 0.02267169952392578s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for DailyMed took 0.00010251998901367188s
Believability | Calculation of trust value for DailyMed took 1.2159347534179688e-05s
INFO | --- Analysis for fu-berlin-dailymed took 143.09262371063232s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.6881978511810303s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.00039076805114746094s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 19.15022349357605s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.021277427673339844s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 9.202957153320312e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.5974044799804688e-05s
INFO | --- Analysis for fu-berlin-dblp took 129.9063572883606s
Availability | SPARQL endpoint availability check for Diseasome took 0.6559309959411621s
Availability | VoID file availability check for Diseasome took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Diseasome took 25.737597465515137s
Reputation | Calculation of the PageRank for Diseasome took 0.02193593978881836s
Interlinking | Calculation of Degree of Connection for Diseasome took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0011508464813232422s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.0001494884490966797s
Believability | Calculation of trust value for Diseasome took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-diseasome took 94.55141282081604s
Availability | SPARQL endpoint availability check for DrugBank took 0.7150774002075195s
Availability | VoID file availability check for DrugBank took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for DrugBank took 0.3875434398651123s
Reputation | Calculation of the PageRank for DrugBank took 0.021179914474487305s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00012350082397460938s
Believability | Calculation of trust value for DrugBank took 1.2636184692382812e-05s
INFO | --- Analysis for fu-berlin-drugbank took 105.32139301300049s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.6827878952026367s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 18.73306941986084s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.02205038070678711s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.337860107421875e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.33514404296875e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 82.27920055389404s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 1.6708755493164062s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 19.47306227684021s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.02172994613647461s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 9.703636169433594e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 9.775161743164062e-06s
INFO | --- Analysis for fu-berlin-euraxess took 171.0374014377594s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.7766244411468506s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0004105567932128906s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 26.35029125213623s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.02139425277709961s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 8.535385131835938e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 5.245208740234375e-06s
INFO | --- Analysis for fu-berlin-eures took 121.48965001106262s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.6562025547027588s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 20.669669151306152s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.021674394607543945s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 0.00011157989501953125s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 7.62939453125e-06s
INFO | --- Analysis for fu-berlin-eurostat took 133.01415181159973s
Availability | SPARQL endpoint availability check for MediCare took 0.6658689975738525s
Availability | VoID file availability check for MediCare took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for MediCare took 0.31180238723754883s
Reputation | Calculation of the PageRank for MediCare took 0.021303176879882812s
Interlinking | Calculation of Degree of Connection for MediCare took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for MediCare took 5.91278076171875e-05s
Believability | Calculation of trust value for MediCare took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-medicare took 71.26500701904297s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.6921465396881104s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 18.999027013778687s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.021071672439575195s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 8.535385131835938e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 1.2159347534179688e-05s
INFO | --- Analysis for fu-berlin-project-gutenberg took 174.54331159591675s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.6715548038482666s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.32369399070739746s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.022143840789794922s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 0.0001010894775390625s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.2159347534179688e-05s
INFO | --- Analysis for fu-berlin-sider took 78.02400279045105s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.6769554615020752s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 26.5993013381958s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.02098250389099121s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.891654968261719e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.2159347534179688e-05s
INFO | --- Analysis for fu-berlin-stitch took 138.60186100006104s
Availability | SPARQL endpoint availability check for fvdb took 9.202957153320312e-05s
Availability | VoID file availability check for fvdb took 0.0011653900146484375s
Completeness | Calculation of interlinking completeness for fvdb took 0.29117345809936523s
Reputation | Calculation of the PageRank for fvdb took 0.021064281463623047s
Interlinking | Calculation of Degree of Connection for fvdb took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.4809112548828125e-05s
Believability | Calculation of trust value for fvdb took 1.1920928955078125e-05s
INFO | --- Analysis for fv took 107.3372859954834s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 9.512901306152344e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0007472038269042969s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 20.230119943618774s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.021655559539794922s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.910064697265625e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 1.1920928955078125e-05s
INFO | --- Analysis for GACS took 204.3989019393921s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.00011968612670898438s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0008831024169921875s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.3124368190765381s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.021181344985961914s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.887580871582031e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.8835067749023438e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 121.87033820152283s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 4.410743713378906e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.3525393009185791s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.021300554275512695s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00010085105895996094s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.1444091796875e-05s
INFO | --- Analysis for garnicaplywood took 161.63052344322205s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.00014543533325195312s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007672309875488281s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.33798933029174805s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.021388530731201172s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.00010776519775390625s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 8.106231689453125e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 164.37418723106384s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.38548994064331055s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.8895788192749023s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 23.12322187423706s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.021167755126953125s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 0.000110626220703125s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for gemet took 175.8028678894043s
Availability | SPARQL endpoint availability check for gemet-annotated took 9.72747802734375e-05s
Availability | VoID file availability check for gemet-annotated took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for gemet-annotated took 18.50201153755188s
Reputation | Calculation of the PageRank for gemet-annotated took 0.021572351455688477s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0008356571197509766s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 5.1975250244140625e-05s
Believability | Calculation of trust value for gemet-annotated took 1.239776611328125e-05s
INFO | --- Analysis for gemet-annotated took 128.05727362632751s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.555551290512085s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 23.79882001876831s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.022324323654174805s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 5.030632019042969e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.430511474609375e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 149.1258225440979s
Availability | SPARQL endpoint availability check for Super Ontology took 0.7352428436279297s
Availability | VoID file availability check for Super Ontology took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.35381507873535156s
Reputation | Calculation of the PageRank for Super Ontology took 0.021561622619628906s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 4.2438507080078125e-05s
Believability | Calculation of trust value for Super Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 196.8783507347107s
Availability | SPARQL endpoint availability check for Geographic detector model took 0.0001087188720703125s
Availability | VoID file availability check for Geographic detector model took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for Geographic detector model took 27.203402519226074s
Reputation | Calculation of the PageRank for Geographic detector model took 0.022253990173339844s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 4.1961669921875e-05s
Believability | Calculation of trust value for Geographic detector model took 1.2159347534179688e-05s
INFO | --- Analysis for GeoDetector took 152.46450781822205s
Availability | SPARQL endpoint availability check for geodomainwn took 9.679794311523438e-05s
Availability | VoID file availability check for geodomainwn took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for geodomainwn took 28.134353160858154s
Reputation | Calculation of the PageRank for geodomainwn took 0.027851343154907227s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0015947818756103516s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 8.535385131835938e-05s
Believability | Calculation of trust value for geodomainwn took 7.867813110351562e-06s
INFO | --- Analysis for geodomainwn took 134.98127675056458s
Availability | SPARQL endpoint availability check for GeoEcuador took 20.0280020236969s
Availability | VoID file availability check for GeoEcuador took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for GeoEcuador took 27.27700924873352s
Reputation | Calculation of the PageRank for GeoEcuador took 0.02117919921875s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 8.440017700195312e-05s
Believability | Calculation of trust value for GeoEcuador took 1.2636184692382812e-05s
INFO | --- Analysis for geoecuador took 226.44623851776123s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 2.783569812774658s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0013041496276855469s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.3209056854248047s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.02163243293762207s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 7.987022399902344e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.2636184692382812e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 333.67681193351746s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.47635412216186523s
Availability | VoID file availability check for GeoLinkedData took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 20.468120098114014s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.02191448211669922s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0008394718170166016s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 0.00011014938354492188s
Believability | Calculation of trust value for GeoLinkedData took 8.344650268554688e-06s
INFO | --- Analysis for geolinkeddata took 118.2135717868805s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.20774221420288086s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0005459785461425781s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 9.22451639175415s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.4012932777404785s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.155731201171875s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.4925696849822998s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.2504136562347412s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.1791987419128418s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.21560263633728027s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.0933225154876709s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.10161852836608887s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.06169486045837402s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.10760021209716797s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 2.4240992069244385s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.10165166854858398s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.09943675994873047s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.13103842735290527s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.10705757141113281s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.07353591918945312s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.10363149642944336s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.293255805969238s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 8.177757263183594e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.07040786743164062s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.07695412635803223s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.09301519393920898s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.07008576393127441s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.07009625434875488s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1646101474761963s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.17780470848083496s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.3704185485839844s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 1.1320245265960693s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.09354496002197266s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.0769968032836914s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06188607215881348s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.35201573371887207s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007355690002441406s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.23137736320495605s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.06968116760253906s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.22186923027038574s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5319738388061523s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.2800803184509277s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.6334972381591797s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.7873008251190186s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.1820535659790039s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.0777733325958252s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.1064257621765137s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.37599992752075195s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.02103400230407715s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0008151531219482422s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 9.918212890625e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 0.4171633720397949s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 179.11082363128662s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 0.00010228157043457031s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 19.92473292350769s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.021070241928100586s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0005011558532714844s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.239776611328125e-05s
INFO | --- Analysis for geonames-semantic-web took 122.41753840446472s
Availability | SPARQL endpoint availability check for Geospatial World  took 9.489059448242188e-05s
Availability | VoID file availability check for Geospatial World  took 0.0007758140563964844s
Completeness | Calculation of interlinking completeness for Geospatial World  took 24.392491102218628s
Reputation | Calculation of the PageRank for Geospatial World  took 0.02121877670288086s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00011372566223144531s
Believability | Calculation of trust value for Geospatial World  took 1.3113021850585938e-05s
INFO | --- Analysis for geospatialworld-net took 138.74623203277588s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.6551856994628906s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 26.171656847000122s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.021328210830688477s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00015115737915039062s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 1.2159347534179688e-05s
INFO | --- Analysis for geospecies took 95.95745873451233s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.935264587402344e-05s
Availability | VoID file availability check for GeoWordNet took 0.0008053779602050781s
Completeness | Calculation of interlinking completeness for GeoWordNet took 19.082273721694946s
Reputation | Calculation of the PageRank for GeoWordNet took 0.021287918090820312s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 6.4849853515625e-05s
Believability | Calculation of trust value for GeoWordNet took 1.1920928955078125e-05s
INFO | --- Analysis for geowordnet took 161.60157918930054s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.08473014831542969s
Availability | VoID file availability check for German labor law thesaurus took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.37999987602233887s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.021169662475585938s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.797645568847656e-05s
Believability | Calculation of trust value for German labor law thesaurus took 2.1457672119140625e-05s
INFO | --- Analysis for german-labor-law-thesaurus took 96.82763361930847s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.57763671875e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.31475234031677246s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.021186351776123047s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0008254051208496094s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 5.7220458984375e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.239776611328125e-05s
INFO | --- Analysis for germlex took 72.37436699867249s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.3693661689758301s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.28949952125549316s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020838499069213867s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.870529174804688e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.3113021850585938e-05s
INFO | --- Analysis for gesis-thesoz took 87.8775577545166s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.8198981285095215s
Availability | VoID file availability check for Art & Architecture Thesaurus took 2.97827410697937s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 26.014047622680664s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.021090269088745117s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 8.7738037109375e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for getty-aat took 144.40237021446228s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.3312962055206299s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.3717832565307617s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.02121448516845703s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 6.556510925292969e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.1682510375976562e-05s
INFO | --- Analysis for getty-tgn took 83.78896355628967s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 7.12359881401062s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0011496543884277344s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.30681657791137695s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.022286653518676758s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0011963844299316406s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 5.221366882324219e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 9.298324584960938e-06s
INFO | --- Analysis for gipuzkoademografia took 148.89069604873657s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 9.012222290039062e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 26.019715785980225s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.021017074584960938s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 4.124641418457031e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 1.239776611328125e-05s
INFO | --- Analysis for glastonbury-2011 took 166.8234565258026s
Availability | SPARQL endpoint availability check for Global Change Information System took 40.031084299087524s
Availability | VoID file availability check for Global Change Information System took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.3020017147064209s
Reputation | Calculation of the PageRank for Global Change Information System took 0.022370100021362305s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 4.1961669921875e-05s
Believability | Calculation of trust value for Global Change Information System took 1.4066696166992188e-05s
INFO | --- Analysis for global-change-information-system took 209.60905361175537s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 9.059906005859375e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0007791519165039062s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 25.41725206375122s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.021506547927856445s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 7.176399230957031e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 1.2636184692382812e-05s
INFO | --- Analysis for global-hunger-index-2011 took 134.60973715782166s
Availability | SPARQL endpoint availability check for Glottolog took 0.00010061264038085938s
Availability | VoID file availability check for Glottolog took 0.0007224082946777344s
Completeness | Calculation of interlinking completeness for Glottolog took 24.440587759017944s
Reputation | Calculation of the PageRank for Glottolog took 0.022667884826660156s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Glottolog took 6.747245788574219e-05s
Believability | Calculation of trust value for Glottolog took 1.2159347534179688e-05s
INFO | --- Analysis for glottolog took 186.82364058494568s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.744529724121094e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.6228504180908203s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.31968140602111816s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.021335363388061523s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.0001220703125s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.239776611328125e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 97.13237357139587s
Availability | SPARQL endpoint availability check for 1121 took 9.322166442871094e-05s
Availability | VoID file availability check for 1121 took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for 1121 took 25.431322813034058s
Reputation | Calculation of the PageRank for 1121 took 0.02120828628540039s
Interlinking | Calculation of Degree of Connection for 1121 took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.552436828613281e-05s
Believability | Calculation of trust value for 1121 took 1.1444091796875e-05s
INFO | --- Analysis for God_ took 114.23602676391602s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 0.0001304149627685547s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 23.197962045669556s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.02131795883178711s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 6.961822509765625e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.2159347534179688e-05s
INFO | --- Analysis for gold took 151.6091604232788s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 6.437301635742188e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 19.5363826751709s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.021442174911499023s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 8.320808410644531e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 1.3828277587890625e-05s
INFO | --- Analysis for googleart-wrapper took 182.3220090866089s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.10219120979309082s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0007541179656982422s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.3781726360321045s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.02149176597595215s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 4.935264587402344e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.2636184692382812e-05s
INFO | --- Analysis for govagribus-denmark took 207.17264080047607s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.3827953338623047s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.3051154613494873s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.022332429885864258s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 9.441375732421875e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 1.0728836059570312e-05s
INFO | --- Analysis for government-web-integration-for-linked-data took 134.82366299629211s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.5980634689331055s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0004031658172607422s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.3695812225341797s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.02089667320251465s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 9.655952453613281e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 9.775161743164062e-06s
INFO | --- Analysis for govtrack took 112.91478252410889s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 9.465217590332031e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 19.421587705612183s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.021956682205200195s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 9.632110595703125e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.3113021850585938e-05s
INFO | --- Analysis for greek-administrative-geography took 139.0170452594757s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.14979982376098633s
Availability | VoID file availability check for Greek Wordnet took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 20.711066246032715s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.02248692512512207s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.410743713378906e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.239776611328125e-05s
INFO | --- Analysis for greek-wordnet took 135.58116841316223s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.3836376667022705s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0006661415100097656s
Extra | Recovery of all triples for Greek prisons releases Jan 2018 - Dec 2023 took 17.236594676971436s
Performance | Total latancy measurement for Greek prisons releases Jan 2018 - Dec 2023 took 0.6184070110321045s
Amount of data | Number of triples check for Greek prisons releases Jan 2018 - Dec 2023 took 0.7584121227264404s
Interoperability | New terms check for Greek prisons releases Jan 2018 - Dec 2023 took 2.0545222759246826s
Versatility | Languages check for Greek prisons releases Jan 2018 - Dec 2023 took 2.275259256362915s
Interpretability | Number of blank nodes check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5954668521881104s
Interpretability | RDF structures check for Greek prisons releases Jan 2018 - Dec 2023 took 0.14374876022338867s
Versatility | Serialization formats check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13003873825073242s
Availability | RDF dump link check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11636996269226074s
License | MR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12637090682983398s
License | HR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5596742630004883s
Amount of data | Number of property check for Greek prisons releases Jan 2018 - Dec 2023 took 0.15708303451538086s
Understandability | Number of label check for Greek prisons releases Jan 2018 - Dec 2023 took 0.19130325317382812s
Understandability | URI regex check for Greek prisons releases Jan 2018 - Dec 2023 took 0.24874186515808105s
Understandability | Vocabs check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12665796279907227s
Verifiability | Authors check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1334834098815918s
Verifiability | Publishers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1181182861328125s
Performance | Throughput check for Greek prisons releases Jan 2018 - Dec 2023 took 10.436092376708984s
Amount of data | Check the number of entities for Greek prisons releases Jan 2018 - Dec 2023 took 0.00015592575073242188s
Verifiability | Contribs. check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11744999885559082s
Interlinking | sameAs chians check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13166379928588867s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1167905330657959s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11666083335876465s
Timeliness | dataset update frequency check for Greek prisons releases Jan 2018 - Dec 2023 took 0.124267578125s
Currency | Creation date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.2458176612854004s
Currency | Modification date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.2626814842224121s
Rep.Conc. | URIs length for Greek prisons releases Jan 2018 - Dec 2023 took 8.108450889587402s
Interoperability | New vocabularies check for Greek prisons releases Jan 2018 - Dec 2023 took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12639808654785156s
Accuracy | Check Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.12306356430053711s
Accuracy | Check Inverse Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.11501240730285645s
Accuracy | Check Empty annotation labels for Greek prisons releases Jan 2018 - Dec 2023 took 2.4180123805999756s
Accuracy | Check White space in annotation for Greek prisons releases Jan 2018 - Dec 2023 took 0.28835535049438477s
Accuracy | Check Datatype consistency for Greek prisons releases Jan 2018 - Dec 2023 took 4.763412714004517s
Consistency | Disjoint class check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1173849105834961s
Consistency | Check Misplaced properties for Greek prisons releases Jan 2018 - Dec 2023 took 1.1782329082489014s
Consistency | Check Ontology hijacking for Greek prisons releases Jan 2018 - Dec 2023 took 3.113144874572754s
Consistency | Check Invalid usage of undefined classes for Greek prisons releases Jan 2018 - Dec 2023 took 1.3970365524291992s
Consistency | Check Invalid usage of undefined properties for Greek prisons releases Jan 2018 - Dec 2023 took 2.617227792739868s
Conciseness | Check Extensional conciseness for Greek prisons releases Jan 2018 - Dec 2023 took 2.9229681491851807s
Security | Sign check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12401723861694336s
Availability | Check URIs Dereferenciability for Greek prisons releases Jan 2018 - Dec 2023 took 4842.8219747543335s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 28.410135746002197s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.022731304168701172s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 2.2411346435546875e-05s
Interoperability | Check the re-using of existing vocabs for Greek prisons releases Jan 2018 - Dec 2023 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 2.4080276489257812e-05s
INFO | --- Analysis for greek_prisons_releases took 5044.091965198517s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.741389274597168s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 21.94281506538391s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020911693572998047s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.034706115722656e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.4066696166992188e-05s
INFO | --- Analysis for greekchildrensartmuseum took 134.24167847633362s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.76837158203125e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.9012515544891357s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.30195188522338867s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.021331071853637695s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00010514259338378906s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.2159347534179688e-05s
INFO | --- Analysis for green-competitiveness-gnoss took 149.5617561340332s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.415259838104248s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 27.748701333999634s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.021229028701782227s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 5.0067901611328125e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 4.57763671875e-05s
INFO | --- Analysis for grrp took 173.0190291404724s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.7829809188842773s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 20.061567306518555s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.021178245544433594s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 8.511543273925781e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 9.059906005859375e-06s
INFO | --- Analysis for grrt took 138.59575247764587s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.1054861545562744s
Availability | VoID file availability check for Geological Timescale took 0.0007460117340087891s
Extra | Recovery of all triples for Geological Timescale took 2.551996946334839s
Performance | Total latancy measurement for Geological Timescale took 4.46204137802124s
Amount of data | Number of triples check for Geological Timescale took 1.0343079566955566s
Interoperability | New terms check for Geological Timescale took 2.5698869228363037s
Versatility | Languages check for Geological Timescale took 0.5096814632415771s
Interpretability | Number of blank nodes check for Geological Timescale took 1.0125114917755127s
Security | Check HTTPS for Geological Timescale took 0.9388895034790039s
Interpretability | RDF structures check for Geological Timescale took 0.9953324794769287s
Versatility | Serialization formats check for Geological Timescale took 1.1628634929656982s
Availability | RDF dump link check for Geological Timescale took 1.7461929321289062s
License | MR license check for Geological Timescale took 0.4705045223236084s
License | HR license check for Geological Timescale took 1.0804393291473389s
Amount of data | Number of property check for Geological Timescale took 0.4804079532623291s
Understandability | Number of label check for Geological Timescale took 0.48581433296203613s
Understandability | URI regex check for Geological Timescale took 1.9581153392791748s
Understandability | Vocabs check for Geological Timescale took 1.1565232276916504s
Verifiability | Authors check for Geological Timescale took 1.0154216289520264s
Verifiability | Publishers check for Geological Timescale took 1.0205779075622559s
Performance | Throughput check for Geological Timescale took 15.612249851226807s
Amount of data | Check the number of entities for Geological Timescale took 0.02229166030883789s
Verifiability | Contribs. check for Geological Timescale took 0.9990291595458984s
Interlinking | sameAs chians check for Geological Timescale took 0.9673738479614258s
Interlinking | skos check for Geological Timescale took 0.9609971046447754s
Interlinking | skos check for Geological Timescale took 0.937861442565918s
Timeliness | dataset update frequency check for Geological Timescale took 1.0134170055389404s
Currency | Creation date check for Geological Timescale took 2.024603843688965s
Currency | Modification date check for Geological Timescale took 1.1483120918273926s
Rep.Conc. | URIs length for Geological Timescale took 2.7227232456207275s
Interoperability | New vocabularies check for Geological Timescale took 2.8561668395996094s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 1.0081405639648438s
Accuracy | Check Functional Property for Geological Timescale took 1.0030148029327393s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.416506290435791s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.3670220375061035s
Accuracy | Check White space in annotation for Geological Timescale took 0.01566338539123535s
Accuracy | Check Datatype consistency for Geological Timescale took 0.0765690803527832s
Consistency | Disjoint class check for Geological Timescale took 0.9680526256561279s
Consistency | Check Misplaced properties for Geological Timescale took 1.9906742572784424s
Consistency | Misplaced classes for Geological Timescale took 1.1173744201660156s
Consistency | Check Ontology hijacking for Geological Timescale took 2.3767244815826416s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.355482578277588s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 1.821686029434204s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.051666975021362305s
Conciseness | Check Intensional conciseness for Geological Timescale took 1.016996145248413s
Security | Sign check for Geological Timescale took 1.0122685432434082s
Availability | Check URIs Dereferenciability for Geological Timescale took 2.839327096939087s
Completeness | Calculation of interlinking completeness for Geological Timescale took 25.352008819580078s
Reputation | Calculation of the PageRank for Geological Timescale took 0.021144390106201172s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0008640289306640625s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 9.512901306152344e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 18.305761575698853s
Believability | Calculation of trust value for Geological Timescale took 1.049041748046875e-05s
INFO | --- Analysis for GTS took 243.35892248153687s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 0.00010824203491210938s
Availability | VoID file availability check for Geological Timescale Ontology took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.3389122486114502s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.021631956100463867s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0009407997131347656s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 5.435943603515625e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.71661376953125e-05s
INFO | --- Analysis for GTS-ont took 134.12624216079712s
Availability | SPARQL endpoint availability check for GUTSTOK  took 7.104873657226562e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 27.054614782333374s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.02137446403503418s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.814697265625e-05s
Believability | Calculation of trust value for GUTSTOK  took 7.62939453125e-06s
INFO | --- Analysis for Guillaume_Forget took 125.37388181686401s
Availability | SPARQL endpoint availability check for Project Gutenberg took 0.00017547607421875s
Availability | VoID file availability check for Project Gutenberg took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 21.304951190948486s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.021127700805664062s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 7.891654968261719e-05s
Believability | Calculation of trust value for Project Gutenberg took 1.2636184692382812e-05s
INFO | --- Analysis for gutenberg took 143.037043094635s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.38690185546875e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0008678436279296875s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 26.322611331939697s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.02131366729736328s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0009164810180664062s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 4.2438507080078125e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.33514404296875e-05s
INFO | --- Analysis for gwa-ili took 120.1261477470398s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.506111145019531e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 21.67719793319702s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.021261930465698242s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 8.678436279296875e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 8.106231689453125e-06s
INFO | --- Analysis for GWR took 133.20511412620544s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 8.988380432128906e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0008192062377929688s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 25.457927465438843s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.021776914596557617s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 5.14984130859375e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 7.62939453125e-06s
INFO | --- Analysis for HASM took 253.39221906661987s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 6.890296936035156e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.31536197662353516s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.022265195846557617s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.981590270996094e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 1.2874603271484375e-05s
INFO | --- Analysis for hcls-knowledge-base took 116.46975946426392s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 2.7446630001068115s
Availability | VoID file availability check for HealthCare Ontology took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 24.072457790374756s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.02137470245361328s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 4.00543212890625e-05s
Believability | Calculation of trust value for HealthCare Ontology took 9.298324584960938e-06s
INFO | --- Analysis for HealthCare_Ontology took 77.91241431236267s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 5.412101745605469e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.3090810775756836s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.023192167282104492s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 7.748603820800781e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 1.239776611328125e-05s
INFO | --- Analysis for heartfailure took 108.26300001144409s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.657415866851807s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007915496826171875s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.31553101539611816s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0222470760345459s
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.3828277587890625e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 5.8650970458984375e-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.2874603271484375e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 191.68828582763672s
Availability | SPARQL endpoint availability check for Hedatuz took 0.27057647705078125s
Availability | VoID file availability check for Hedatuz took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Hedatuz took 21.96288824081421s
Reputation | Calculation of the PageRank for Hedatuz took 0.02241230010986328s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 9.72747802734375e-05s
Believability | Calculation of trust value for Hedatuz took 1.1920928955078125e-05s
INFO | --- Analysis for hedatuz took 150.82652854919434s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.10821318626403809s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2852301597595215s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.02114415168762207s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00014829635620117188s
Believability | Calculation of trust value for Hellenic Fire Brigade took 9.298324584960938e-06s
INFO | --- Analysis for hellenic-fire-brigade took 125.8740451335907s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.025362014770507812s
Availability | VoID file availability check for Hellenic Police took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Hellenic Police took 26.58217453956604s
Reputation | Calculation of the PageRank for Hellenic Police took 0.021816253662109375s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00013256072998046875s
Believability | Calculation of trust value for Hellenic Police took 5.245208740234375e-06s
INFO | --- Analysis for hellenic-police took 52.02714776992798s
Availability | SPARQL endpoint availability check for Hermos took 0.00011515617370605469s
Availability | VoID file availability check for Hermos took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Hermos took 0.31136274337768555s
Reputation | Calculation of the PageRank for Hermos took 0.021376371383666992s
Interlinking | Calculation of Degree of Connection for Hermos took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0008051395416259766s
Interlinking | Calculation of Clustering coefficient for Hermos took 4.076957702636719e-05s
Believability | Calculation of trust value for Hermos took 8.344650268554688e-06s
INFO | --- Analysis for Hermos took 103.79072165489197s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 0.00010561943054199219s
Availability | VoID file availability check for Himanshu Mahawar took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.34856748580932617s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.0213468074798584s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 3.7670135498046875e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 1.239776611328125e-05s
INFO | --- Analysis for Himanshu_Mahawar took 175.26499557495117s
Availability | SPARQL endpoint availability check for HITO took 0.4221217632293701s
Availability | VoID file availability check for HITO took 0.0007145404815673828s
Extra | Recovery of all triples for HITO took 2.135960817337036s
Performance | Total latancy measurement for HITO took 0.9699723720550537s
Amount of data | Number of triples check for HITO took 0.17949271202087402s
Interoperability | New terms check for HITO took 1.5985655784606934s
Versatility | Languages check for HITO took 0.22524762153625488s
Interpretability | Number of blank nodes check for HITO took 0.17762374877929688s
Interpretability | RDF structures check for HITO took 0.20511341094970703s
Versatility | Serialization formats check for HITO took 0.18838167190551758s
Availability | RDF dump link check for HITO took 0.1875929832458496s
License | MR license check for HITO took 0.20844340324401855s
License | HR license check for HITO took 0.19358396530151367s
Amount of data | Number of property check for HITO took 0.20357680320739746s
Understandability | Number of label check for HITO took 0.2076435089111328s
Understandability | URI regex check for HITO took 0.3640022277832031s
Understandability | Vocabs check for HITO took 0.1808319091796875s
Verifiability | Authors check for HITO took 0.2049422264099121s
Verifiability | Publishers check for HITO took 0.19931244850158691s
Performance | Throughput check for HITO took 11.387555122375488s
Amount of data | Check the number of entities for HITO took 5.9604644775390625e-05s
Verifiability | Contribs. check for HITO took 0.1888880729675293s
Interlinking | sameAs chians check for HITO took 0.17909002304077148s
Interlinking | skos check for HITO took 0.2042708396911621s
Interlinking | skos check for HITO took 0.16991829872131348s
Timeliness | dataset update frequency check for HITO took 0.19470906257629395s
Currency | Creation date check for HITO took 0.38904857635498047s
Currency | Modification date check for HITO took 0.38535308837890625s
Rep.Conc. | URIs length for HITO took 1.1068041324615479s
Interoperability | New vocabularies check for HITO took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.1833970546722412s
Accuracy | Check Functional Property for HITO took 0.20920419692993164s
Accuracy | Check Inverse Functional Property for HITO took 0.21190190315246582s
Accuracy | Check Empty annotation labels for HITO took 0.5091776847839355s
Accuracy | Check White space in annotation for HITO took 0.013512134552001953s
Accuracy | Check Datatype consistency for HITO took 0.0781106948852539s
Consistency | Disjoint class check for HITO took 0.18289828300476074s
Consistency | Check Misplaced properties for HITO took 0.4878060817718506s
Consistency | Misplaced classes for HITO took 0.3844428062438965s
Consistency | Check Ontology hijacking for HITO took 1.837944746017456s
Consistency | Check Invalid usage of undefined classes for HITO took 1.3621716499328613s
Consistency | Check Invalid usage of undefined properties for HITO took 3.1327667236328125s
Conciseness | Check Extensional conciseness for HITO took 0.06614351272583008s
Conciseness | Check Intensional conciseness for HITO took 3.4021506309509277s
Security | Sign check for HITO took 3.421658754348755s
Availability | Check URIs Dereferenciability for HITO took 3313.206073999405s
Completeness | Calculation of interlinking completeness for HITO took 0.3590977191925049s
Reputation | Calculation of the PageRank for HITO took 0.021944284439086914s
Interlinking | Calculation of Degree of Connection for HITO took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for HITO took 8.916854858398438e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.430511474609375e-06s
Believability | Calculation of trust value for HITO took 1.2636184692382812e-05s
INFO | --- Analysis for hito took 3483.975861787796s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 16.57039999961853s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.29328155517578125s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.02130293846130371s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 3.266334533691406e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 1.2636184692382812e-05s
INFO | --- Analysis for Hoa_Thinh_Phat took 179.68643069267273s
Availability | SPARQL endpoint availability check for Homologene took 4.744529724121094e-05s
Availability | VoID file availability check for Homologene took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for Homologene took 0.33533740043640137s
Reputation | Calculation of the PageRank for Homologene took 0.021590709686279297s
Interlinking | Calculation of Degree of Connection for Homologene took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Homologene took 0.00084686279296875s
Interlinking | Calculation of Clustering coefficient for Homologene took 4.57763671875e-05s
Believability | Calculation of trust value for Homologene took 1.4543533325195312e-05s
INFO | --- Analysis for homologene took 162.8510127067566s
Availability | SPARQL endpoint availability check for gseg took 9.322166442871094e-05s
Availability | VoID file availability check for gseg took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for gseg took 27.47610116004944s
Reputation | Calculation of the PageRank for gseg took 0.02106022834777832s
Interlinking | Calculation of Degree of Connection for gseg took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for gseg took 4.172325134277344e-05s
Believability | Calculation of trust value for gseg took 1.239776611328125e-05s
INFO | --- Analysis for hongse took 177.52950143814087s
Availability | SPARQL endpoint availability check for Noticias Universia took 8.678436279296875e-05s
Availability | VoID file availability check for Noticias Universia took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Noticias Universia took 23.101824045181274s
Reputation | Calculation of the PageRank for Noticias Universia took 0.021044015884399414s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 4.601478576660156e-05s
Believability | Calculation of trust value for Noticias Universia took 1.3589859008789062e-05s
INFO | --- Analysis for http-data-noticias-universia-net took 101.88190460205078s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 8.916854858398438e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.3024604320526123s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.021140098571777344s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 3.910064697265625e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.239776611328125e-05s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 77.54656720161438s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 3.3633501529693604s
Availability | VoID file availability check for COURAGE Dataset took 0.0007188320159912109s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 23.26725459098816s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.021758556365966797s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.3855438232421875e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.0728836059570312e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 158.16784977912903s
Availability | SPARQL endpoint availability check for RoadTrb took 0.0001785755157470703s
Availability | VoID file availability check for RoadTrb took 0.000293731689453125s
Completeness | Calculation of interlinking completeness for RoadTrb took 25.18621826171875s
Reputation | Calculation of the PageRank for RoadTrb took 0.02126622200012207s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.790855407714844e-05s
Believability | Calculation of trust value for RoadTrb took 1.3828277587890625e-05s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 134.77277064323425s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0007541179656982422s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.3118278980255127s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.021648168563842773s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 4.744529724121094e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 105.7523820400238s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 5.2928924560546875e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.32748961448669434s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.021176815032958984s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.314018249511719e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.2159347534179688e-05s
INFO | --- Analysis for http:pakistan.com took 53.32878017425537s
Availability | SPARQL endpoint availability check for CEDICT took 9.393692016601562e-05s
Availability | VoID file availability check for CEDICT took 0.0007491111755371094s
Completeness | Calculation of interlinking completeness for CEDICT took 26.484290599822998s
Reputation | Calculation of the PageRank for CEDICT took 0.02112579345703125s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.528594970703125e-05s
Believability | Calculation of trust value for CEDICT took 8.344650268554688e-06s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 84.49071621894836s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.214414596557617s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 27.24105429649353s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.021119117736816406s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.486343383789062e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.2159347534179688e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 138.5093674659729s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 9.202957153320312e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 25.750282049179077s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.021126270294189453s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 4.2438507080078125e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 1.621246337890625e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 201.95654916763306s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.839897155761719e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 22.611942529678345s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.021123647689819336s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0008018016815185547s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 4.220008850097656e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.2636184692382812e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 119.8956880569458s
Availability | SPARQL endpoint availability check for Soccer Dataset took 9.274482727050781e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.3140857219696045s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.022642850875854492s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.981590270996094e-05s
Believability | Calculation of trust value for Soccer Dataset took 7.152557373046875e-06s
INFO | --- Analysis for http:www.msm.com took 145.5797073841095s
Availability | SPARQL endpoint availability check for Game Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Game Ontology took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Game Ontology took 26.30463147163391s
Reputation | Calculation of the PageRank for Game Ontology took 0.021452665328979492s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 4.029273986816406e-05s
Believability | Calculation of trust value for Game Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for http:www.RAG.comgameonto# took 124.11717128753662s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.632110595703125e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.28044772148132324s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.021086692810058594s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007681846618652344s
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.1920928955078125e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 77.84181427955627s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.506111145019531e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.00034499168395996094s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 24.926730632781982s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.03083348274230957s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.482269287109375e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.049041748046875e-05s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 144.235737323761s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.179115295410156e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 23.643860816955566s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020956039428710938s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.981590270996094e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1920928955078125e-05s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 97.94350600242615s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.226799011230469e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3325493335723877s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02121734619140625s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.504753112792969e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2636184692382812e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 121.21533679962158s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 6.67572021484375e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.29944467544555664s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.0216825008392334s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 4.267692565917969e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2636184692382812e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 150.49360132217407s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.00010228157043457031s
Availability | VoID file availability check for Indian Biodiversity took 0.0006985664367675781s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.37133264541625977s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021142244338989258s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.4332275390625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2874603271484375e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 124.67334413528442s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.00010180473327636719s
Availability | VoID file availability check for Indian Biodiversity took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2899806499481201s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021250009536743164s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.2901763916015625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1920928955078125e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 177.34738159179688s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 5.0067901611328125e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 25.126982927322388s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.021266698837280273s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.100799560546875e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.1682510375976562e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 184.62834548950195s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.071187973022461s
Availability | VoID file availability check for Bookkeeping took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for Bookkeeping took 23.60033082962036s
Reputation | Calculation of the PageRank for Bookkeeping took 0.021494626998901367s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.886222839355469e-05s
Believability | Calculation of trust value for Bookkeeping took 1.1682510375976562e-05s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 143.0186800956726s
Availability | SPARQL endpoint availability check for Legal Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Legal Ontology took 0.0003044605255126953s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.30779314041137695s
Reputation | Calculation of the PageRank for Legal Ontology took 0.021131515502929688s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 4.4345855712890625e-05s
Believability | Calculation of trust value for Legal Ontology took 7.867813110351562e-06s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 109.70620632171631s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 8.988380432128906e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.3111581802368164s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.021291732788085938s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 9.34600830078125e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.2159347534179688e-05s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 102.30965900421143s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.458427429199219e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.42638540267944336s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.02135944366455078s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 3.8623809814453125e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 1.239776611328125e-05s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 110.92408108711243s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 0.0004870891571044922s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 30.28239345550537s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.021017789840698242s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 3.266334533691406e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 1.33514404296875e-05s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 164.77938532829285s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.9115045070648193s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.341752290725708s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.021390438079833984s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 4.172325134277344e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 1.33514404296875e-05s
INFO | --- Analysis for hud-library-usagedata took 102.87563562393188s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 0.40443992614746094s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.00030541419982910156s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 22.234567403793335s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.02929544448852539s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00011491775512695312s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 7.867813110351562e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 119.72560811042786s
Availability | SPARQL endpoint availability check for IATE RDF took 4.673004150390625e-05s
Availability | VoID file availability check for IATE RDF took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for IATE RDF took 23.227110147476196s
Reputation | Calculation of the PageRank for IATE RDF took 0.022519588470458984s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 4.57763671875e-05s
Believability | Calculation of trust value for IATE RDF took 1.2159347534179688e-05s
INFO | --- Analysis for iate-rdf took 95.78968286514282s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.337247610092163s
Availability | VoID file availability check for IATI as Linked Data took 0.00072479248046875s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.2808811664581299s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.023201704025268555s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 9.131431579589844e-05s
Believability | Calculation of trust value for IATI as Linked Data took 1.3589859008789062e-05s
INFO | --- Analysis for iati-as-linked-data took 164.33239364624023s
Availability | SPARQL endpoint availability check for ICANE took 0.26239919662475586s
Availability | VoID file availability check for ICANE took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for ICANE took 0.3036043643951416s
Reputation | Calculation of the PageRank for ICANE took 0.0210874080657959s
Interlinking | Calculation of Degree of Connection for ICANE took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for ICANE took 9.369850158691406e-05s
Believability | Calculation of trust value for ICANE took 9.298324584960938e-06s
INFO | --- Analysis for icane took 52.97335958480835s
Availability | SPARQL endpoint availability check for ichoose took 0.12702393531799316s
Availability | VoID file availability check for ichoose took 0.00035452842712402344s
Completeness | Calculation of interlinking completeness for ichoose took 0.3226161003112793s
Reputation | Calculation of the PageRank for ichoose took 0.02158951759338379s
Interlinking | Calculation of Degree of Connection for ichoose took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for ichoose took 9.083747863769531e-05s
Believability | Calculation of trust value for ichoose took 1.2159347534179688e-05s
INFO | --- Analysis for ichoose took 122.16359996795654s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 0.2282724380493164s
Availability | VoID file availability check for The Iconology Dataset took 0.0006716251373291016s
Extra | Recovery of all triples for The Iconology Dataset took 3.540254831314087s
Performance | Total latancy measurement for The Iconology Dataset took 0.4329814910888672s
Amount of data | Number of triples check for The Iconology Dataset took 0.1947927474975586s
Interoperability | New terms check for The Iconology Dataset took 1.5068979263305664s
Versatility | Languages check for The Iconology Dataset took 0.6096980571746826s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.24751067161560059s
Interpretability | RDF structures check for The Iconology Dataset took 0.12636494636535645s
Versatility | Serialization formats check for The Iconology Dataset took 0.10282278060913086s
Availability | RDF dump link check for The Iconology Dataset took 0.0858464241027832s
License | MR license check for The Iconology Dataset took 0.1045541763305664s
License | HR license check for The Iconology Dataset took 0.22554922103881836s
Amount of data | Number of property check for The Iconology Dataset took 0.10002398490905762s
Understandability | Number of label check for The Iconology Dataset took 0.14487648010253906s
Understandability | URI regex check for The Iconology Dataset took 0.1685030460357666s
Understandability | Vocabs check for The Iconology Dataset took 0.08941364288330078s
Verifiability | Authors check for The Iconology Dataset took 0.09801220893859863s
Verifiability | Publishers check for The Iconology Dataset took 0.10493731498718262s
Performance | Throughput check for The Iconology Dataset took 10.379154443740845s
Amount of data | Check the number of entities for The Iconology Dataset took 9.72747802734375e-05s
Verifiability | Contribs. check for The Iconology Dataset took 0.08780956268310547s
Interlinking | sameAs chians check for The Iconology Dataset took 0.08039307594299316s
Interlinking | skos check for The Iconology Dataset took 0.10886740684509277s
Interlinking | skos check for The Iconology Dataset took 0.09232449531555176s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.08960366249084473s
Currency | Creation date check for The Iconology Dataset took 0.18092083930969238s
Currency | Modification date check for The Iconology Dataset took 0.18402385711669922s
Rep.Conc. | URIs length for The Iconology Dataset took 1.2957994937896729s
Interoperability | New vocabularies check for The Iconology Dataset took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.0805673599243164s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.27294039726257324s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.01638340950012207s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.43744707107543945s
Consistency | Disjoint class check for The Iconology Dataset took 0.08530855178833008s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.15884876251220703s
Consistency | Misplaced classes for The Iconology Dataset took 0.8696763515472412s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.6945958137512207s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.3632352352142334s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.439805269241333s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.300004243850708s
Security | Sign check for The Iconology Dataset took 0.0788576602935791s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2530.9716210365295s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 25.90857172012329s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.02287912368774414s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 7.033348083496094e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for The Iconology Dataset took 1.239776611328125e-05s
INFO | --- Analysis for iconology-dataset took 2682.8834393024445s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 0.00018405914306640625s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 25.07803249359131s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.022435665130615234s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 8.821487426757812e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 1.1920928955078125e-05s
INFO | --- Analysis for idreffr took 122.54100632667542s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.699080228805542s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.2900409698486328s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.022039413452148438s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 5.602836608886719e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 8.106231689453125e-06s
INFO | --- Analysis for ids took 106.5368664264679s
Availability | SPARQL endpoint availability check for ietflang took 9.489059448242188e-05s
Availability | VoID file availability check for ietflang took 0.0007512569427490234s
Completeness | Calculation of interlinking completeness for ietflang took 26.756224393844604s
Reputation | Calculation of the PageRank for ietflang took 0.02097606658935547s
Interlinking | Calculation of Degree of Connection for ietflang took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for ietflang took 5.1021575927734375e-05s
Believability | Calculation of trust value for ietflang took 1.1444091796875e-05s
INFO | --- Analysis for ietflang took 135.29021000862122s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.5775833129882812s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 22.89527988433838s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02126789093017578s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 4.696846008300781e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.1444091796875e-05s
INFO | --- Analysis for IGVLL took 127.87818217277527s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.5094287395477295s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.000606536865234375s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.6307528018951416s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9495880603790283s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.2044975757598877s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.581791877746582s
Versatility | Languages check for 3LGM² IHE Ontology took 0.25533318519592285s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.20029807090759277s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.2660708427429199s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.20831680297851562s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.20004916191101074s
License | MR license check for 3LGM² IHE Ontology took 0.23231220245361328s
License | HR license check for 3LGM² IHE Ontology took 0.22100424766540527s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.1883983612060547s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.21703553199768066s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.39536285400390625s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.19421672821044922s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.19414544105529785s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.20389199256896973s
Performance | Throughput check for 3LGM² IHE Ontology took 13.411016941070557s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 0.00012969970703125s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.19510936737060547s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.24310088157653809s
Interlinking | skos check for 3LGM² IHE Ontology took 0.4484288692474365s
Interlinking | skos check for 3LGM² IHE Ontology took 0.8223719596862793s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 1.4439425468444824s
Currency | Creation date check for 3LGM² IHE Ontology took 7.804076910018921s
Currency | Modification date check for 3LGM² IHE Ontology took 6.278348207473755s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 7.125529527664185s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 7.7168402671813965s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 5.460780620574951s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 1.5102925300598145s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 1.4321939945220947s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.0022666454315185547s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.050632476806640625s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 2.5831871032714844s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 5.780635356903076s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 2.876648187637329s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 3.9415645599365234s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.3749825954437256s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.959012746810913s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.03168082237243652s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 2.3610706329345703s
Security | Sign check for 3LGM² IHE Ontology took 3.7250914573669434s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 761.787938117981s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 27.215663194656372s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.022620201110839844s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 4.38690185546875e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.1920928955078125e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for IHE took 1245.6932256221771s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 7.3076300621032715s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0007917881011962891s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 4.134523153305054s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 7.3268842697143555s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 13.978757619857788s
Interoperability | New terms check for Test Site, LOD Lab 317 took 8.452442407608032s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.44195890426636s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 1.620840311050415s
Security | Check HTTPS for Test Site, LOD Lab 317 took 0.9875984191894531s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 1.4967985153198242s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.4933927059173584s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.478593111038208s
License | MR license check for Test Site, LOD Lab 317 took 1.8818068504333496s
License | HR license check for Test Site, LOD Lab 317 took 1.7423210144042969s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.495795726776123s
Understandability | Number of label check for Test Site, LOD Lab 317 took 1.4958109855651855s
Understandability | URI regex check for Test Site, LOD Lab 317 took 2.949726104736328s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.5070738792419434s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.4886524677276611s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 1.4625294208526611s
Performance | Throughput check for Test Site, LOD Lab 317 took 14.686548709869385s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 3.24249267578125e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.4900672435760498s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.4505972862243652s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.538680076599121s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.483947515487671s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.471045732498169s
Currency | Creation date check for Test Site, LOD Lab 317 took 2.986053943634033s
Currency | Modification date check for Test Site, LOD Lab 317 took 2.966404914855957s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 35.86207675933838s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.4892101287841797s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.4677228927612305s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.4671800136566162s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.4595081806182861s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 26.365339756011963s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 1.7271487712860107s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 2.268514633178711s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 24.254825592041016s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.00023412704467773438s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 1.9948039054870605s
Security | Sign check for Test Site, LOD Lab 317 took 1.5085091590881348s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 26.912265062332153s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.021613597869873047s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 4.172325134277344e-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.4543533325195312e-05s
INFO | --- Analysis for iislod-test took 649.9676103591919s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 9.131431579589844e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 23.785080909729004s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.02515125274658203s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.24249267578125e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 1.1920928955078125e-05s
INFO | --- Analysis for ILUSOC took 147.2220332622528s
Availability | SPARQL endpoint availability check for im@sparql took 8.159699201583862s
Availability | VoID file availability check for im@sparql took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for im@sparql took 22.285635948181152s
Reputation | Calculation of the PageRank for im@sparql took 0.021419286727905273s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.361701965332031e-05s
Believability | Calculation of trust value for im@sparql took 1.239776611328125e-05s
INFO | --- Analysis for im@sparql took 102.8706579208374s
Availability | SPARQL endpoint availability check for imagery bailingniao took 0.00011777877807617188s
Availability | VoID file availability check for imagery bailingniao took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.29915714263916016s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.022427797317504883s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.218650817871094e-05s
Believability | Calculation of trust value for imagery bailingniao took 1.1920928955078125e-05s
INFO | --- Analysis for imagery_bailingniao took 98.25372004508972s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.127671718597412s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.6806173324584961s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 19.997735023498535s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.4200711250305176s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 10.07240343093872s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.258448600769043s
Versatility | Languages check for Imagesnippets Image Descriptions took 20.35075044631958s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.329577207565308s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.6731786727905273s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7213950157165527s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7077665328979492s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7129929065704346s
License | MR license check for Imagesnippets Image Descriptions took 0.6833667755126953s
License | HR license check for Imagesnippets Image Descriptions took 30.696789741516113s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7030565738677979s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.5479888916015625s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.3738222122192383s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7062745094299316s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7206182479858398s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7014460563659668s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.533132314682007s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 8.702278137207031e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7221920490264893s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.6843724250793457s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7193303108215332s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6873953342437744s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7228274345397949s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.406432867050171s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.4057073593139648s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 33.87774157524109s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7140579223632812s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.6975216865539551s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7143261432647705s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 12.01209831237793s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.220837116241455s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.434981107711792s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7078654766082764s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.981191158294678s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 5.3209779262542725s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.572089672088623s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.860935926437378s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 2.918637275695801s
Security | Sign check for Imagesnippets Image Descriptions took 0.7042884826660156s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 11.251821041107178s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 21.56816005706787s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.022053956985473633s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.001207113265991211s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 0.00013184547424316406s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.9073486328125e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 1.33514404296875e-05s
INFO | --- Analysis for imagesnippets took 518.6363022327423s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.09955191612243652s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.31372642517089844s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.021471261978149414s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 9.989738464355469e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 1.1444091796875e-05s
INFO | --- Analysis for imf-linked-data took 120.83417892456055s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 9.34600830078125e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 24.002362728118896s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.02270817756652832s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 2.193450927734375e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 1.6927719116210938e-05s
INFO | --- Analysis for Imtiaz took 72.85776662826538s
Availability | SPARQL endpoint availability check for Royalty Free Music took 9.179115295410156e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0008089542388916016s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 27.227553606033325s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.02187323570251465s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 4.315376281738281e-05s
Believability | Calculation of trust value for Royalty Free Music took 1.3589859008789062e-05s
INFO | --- Analysis for inaudio.org took 101.86094212532043s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.585017204284668s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 23.52226710319519s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.021500110626220703s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 4.553794860839844e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for IndexThomisticusTreebank took 169.35645627975464s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0004677772521972656s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 25.846988677978516s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.02111196517944336s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.695487976074219e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.52587890625e-05s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 148.35912466049194s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.00013899803161621094s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.31829166412353516s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.021230697631835938s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.000125885009765625s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 8.106231689453125e-06s
INFO | --- Analysis for ineverycrea took 89.00688099861145s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.00018978118896484375s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.00077056884765625s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.31761598587036133s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.02112603187561035s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0008406639099121094s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.00011754035949707031s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.0728836059570312e-05s
INFO | --- Analysis for ineverycrea-argentina took 140.88925862312317s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 271.13159561157227s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.29203271865844727s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.029016971588134766s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.62939453125e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for influence-tracker-dataset took 740.9906480312347s
Availability | SPARQL endpoint availability check for INSEMTIVES took 0.5004785060882568s
Availability | VoID file availability check for INSEMTIVES took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.3040177822113037s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.021808385848999023s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 3.647804260253906e-05s
Believability | Calculation of trust value for INSEMTIVES took 1.2636184692382812e-05s
INFO | --- Analysis for insemtives took 109.46421957015991s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 9.1552734375e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.35594773292541504s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.021000146865844727s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 3.361701965332031e-05s
Believability | Calculation of trust value for Instance Hub Countries took 1.1682510375976562e-05s
INFO | --- Analysis for instance-hub-countries took 52.6266405582428s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 0.00010251998901367188s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 24.772321701049805s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.021130084991455078s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 4.4345855712890625e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 1.3113021850585938e-05s
INFO | --- Analysis for instance-hub-fiscal-years took 131.2585322856903s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 8.7738037109375e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.31342530250549316s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.0219573974609375s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 3.266334533691406e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 1.239776611328125e-05s
INFO | --- Analysis for instance-hub-organizations took 46.02824640274048s
Availability | SPARQL endpoint availability check for Instance Hub People took 5.030632019042969e-05s
Availability | VoID file availability check for Instance Hub People took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.30744028091430664s
Reputation | Calculation of the PageRank for Instance Hub People took 0.021004199981689453s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 4.482269287109375e-05s
Believability | Calculation of trust value for Instance Hub People took 1.2636184692382812e-05s
INFO | --- Analysis for instance-hub-people took 121.07974863052368s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 4.1961669921875e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 24.883130073547363s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.021094322204589844s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 4.076957702636719e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 2.2172927856445312e-05s
INFO | --- Analysis for instance-hub-us-civil-servants took 146.76935386657715s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.410743713378906e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 21.23691749572754s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.02187967300415039s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.910064697265625e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 1.33514404296875e-05s
INFO | --- Analysis for instance-hub-us-congressional-committees took 137.93858671188354s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 5.340576171875e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 21.67751145362854s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.023462772369384766s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 6.461143493652344e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 1.2636184692382812e-05s
INFO | --- Analysis for instance-hub-us-congressional-districts took 90.62710928916931s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 5.078315734863281e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 22.085280895233154s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.021205425262451172s
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.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.2901763916015625e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 1.239776611328125e-05s
INFO | --- Analysis for instance-hub-us-crops took 136.05816960334778s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 6.937980651855469e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 21.791911125183105s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.025167465209960938s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0013575553894042969s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 6.031990051269531e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 1.3113021850585938e-05s
INFO | --- Analysis for instance-hub-us-federal-agencies took 161.39427518844604s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 7.724761962890625e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.3085789680480957s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.02220630645751953s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.552436828613281e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 1.5497207641601562e-05s
INFO | --- Analysis for instance-hub-us-states-and-territories took 115.2617859840393s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.2438507080078125e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 26.4885995388031s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.02164006233215332s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 4.100799560546875e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 1.1205673217773438e-05s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 151.0974349975586s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 40.03776693344116s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.37520360946655273s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.022745847702026367s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 4.076957702636719e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.1682510375976562e-05s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 150.18561172485352s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.649162292480469e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 25.659271240234375s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.02127838134765625s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0001049041748046875s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.2159347534179688e-05s
INFO | --- Analysis for interactivemaps-gnoss took 105.19939160346985s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 9.036064147949219e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.323789119720459s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.021018028259277344s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.3855438232421875e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 1.2636184692382812e-05s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 117.3454213142395s
Availability | SPARQL endpoint availability check for intervalue took 0.11188268661499023s
Availability | VoID file availability check for intervalue took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for intervalue took 23.04306650161743s
Reputation | Calculation of the PageRank for intervalue took 0.02105998992919922s
Interlinking | Calculation of Degree of Connection for intervalue took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for intervalue took 7.128715515136719e-05s
Believability | Calculation of trust value for intervalue took 1.1920928955078125e-05s
INFO | --- Analysis for intervalue took 102.52033734321594s
Availability | SPARQL endpoint availability check for Inztrow took 4.696846008300781e-05s
Availability | VoID file availability check for Inztrow took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for Inztrow took 21.917124032974243s
Reputation | Calculation of the PageRank for Inztrow took 0.02107071876525879s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.6716461181640625e-05s
Believability | Calculation of trust value for Inztrow took 1.2159347534179688e-05s
INFO | --- Analysis for Inztrow took 75.0061776638031s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 0.000102996826171875s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 21.847534894943237s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.021281003952026367s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for ipbes took 147.6936457157135s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.696846008300781e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 21.57991600036621s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.023442983627319336s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 6.127357482910156e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 1.8835067749023438e-05s
INFO | --- Analysis for iptc-newscodes took 180.6041603088379s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.3424978256225586s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 24.879689693450928s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.021277427673339844s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 0.0001068115234375s
Believability | Calculation of trust value for iServe: Linked Services Registry took 1.1920928955078125e-05s
INFO | --- Analysis for iserve took 154.8375096321106s
Availability | SPARQL endpoint availability check for ISIC V4 took 21.266738891601562s
Availability | VoID file availability check for ISIC V4 took 0.0008788108825683594s
Completeness | Calculation of interlinking completeness for ISIC V4 took 24.056697130203247s
Reputation | Calculation of the PageRank for ISIC V4 took 0.021771907806396484s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 4.9114227294921875e-05s
Believability | Calculation of trust value for ISIC V4 took 1.0013580322265625e-05s
INFO | --- Analysis for isic-v4 took 245.06617498397827s
Availability | SPARQL endpoint availability check for Isidore took 0.00014495849609375s
Availability | VoID file availability check for Isidore took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Isidore took 22.582013845443726s
Reputation | Calculation of the PageRank for Isidore took 0.02159881591796875s
Interlinking | Calculation of Degree of Connection for Isidore took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Isidore took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Isidore took 3.743171691894531e-05s
Believability | Calculation of trust value for Isidore took 1.33514404296875e-05s
INFO | --- Analysis for isidore took 140.16604375839233s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.76837158203125e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.00041985511779785156s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.3199150562286377s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.021347761154174805s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.510185241699219e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 1.0251998901367188e-05s
INFO | --- Analysis for isil-dbpedia took 154.47066235542297s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 4.506111145019531e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.000766754150390625s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 28.40109944343567s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.022236108779907227s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.00084686279296875s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 4.124641418457031e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 1.239776611328125e-05s
INFO | --- Analysis for iso-3166-2-data took 172.70852375030518s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.935264587402344e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.34055495262145996s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.021885156631469727s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 4.220008850097656e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 1.6689300537109375e-05s
INFO | --- Analysis for iso-639-oasis took 133.56781458854675s
Availability | SPARQL endpoint availability check for ISOcat took 9.274482727050781e-05s
Availability | VoID file availability check for ISOcat took 0.001348257064819336s
Completeness | Calculation of interlinking completeness for ISOcat took 0.3134274482727051s
Reputation | Calculation of the PageRank for ISOcat took 0.022929906845092773s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.365776062011719e-05s
Believability | Calculation of trust value for ISOcat took 1.239776611328125e-05s
INFO | --- Analysis for isocat took 78.62113785743713s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 5.1975250244140625e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 26.099153757095337s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020995140075683594s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.9577484130859375e-05s
Believability | Calculation of trust value for ISOcat-metadata took 1.2636184692382812e-05s
INFO | --- Analysis for isocat-metadata took 146.90370202064514s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14538860321044922s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0006554126739501953s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.3010640144348145s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.28423309326171875s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1485586166381836s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.98433518409729s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.70789504051208s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07999205589294434s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0320897102355957s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0984039306640625s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0890970230102539s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08178210258483887s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1364915370941162s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.48392486572266s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08170771598815918s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.316093921661377s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.28352928161621094s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12755060195922852s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12648725509643555s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08076000213623047s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.284677028656006s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.891654968261719e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12114310264587402s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1823711395263672s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3802525997161865s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.36042022705078125s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16027212142944336s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19311237335205078s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08028125762939453s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 12.83201003074646s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08029055595397949s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08478736877441406s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08923649787902832s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.853569507598877s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.31732845306396484s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.27768969535827637s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08037018775939941s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.908438205718994s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9446125030517578s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.8987231254577637s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3944087028503418s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.204239845275879s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.29423069953918457s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08974623680114746s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10431742668151855s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.301213502883911s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.43071484565734863s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.021862268447875977s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00010323524475097656s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3589859008789062e-05s
INFO | --- Analysis for ispra-lod-place took 568.5118336677551s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.051923513412475586s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0005826950073242188s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 5.3759543895721436s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.27291011810302734s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.13598084449768066s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.9993350505828857s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 92.00347423553467s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.08156394958496094s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.0301513671875s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.0969698429107666s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.09632706642150879s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.08435988426208496s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.1320657730102539s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 90.64261651039124s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.08251595497131348s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.2354786396026611s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.28733205795288086s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.12003850936889648s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.12152099609375s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.08238363265991211s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.304083585739136s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 7.367134094238281e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.11939239501953125s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.18351316452026367s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.3853592872619629s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.34400463104248047s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.12211084365844727s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.16680479049682617s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.0801541805267334s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 12.859065055847168s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.08022785186767578s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.09273982048034668s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.08339667320251465s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 2.745839834213257s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.31749796867370605s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.27812862396240234s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.07627320289611816s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 8.928298711776733s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9205653667449951s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 2.941183567047119s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.4004673957824707s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.223610877990723s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.29505062103271484s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.09255170822143555s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.09717679023742676s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 8.436376571655273s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.5456154346466064s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.02170848846435547s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 4.7206878662109375e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.7206878662109375e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.9073486328125e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 1.430511474609375e-05s
INFO | --- Analysis for ispra-lod-ron took 490.1404573917389s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.6789402961730957s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0007493495941162109s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 23.01601219177246s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.021039724349975586s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 0.00010800361633300781s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 1.2636184692382812e-05s
INFO | --- Analysis for issa-agritrop took 80.19907808303833s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.38690185546875e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 23.341226816177368s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020911693572998047s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 4.315376281738281e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.1444091796875e-05s
INFO | --- Analysis for ISSN:0080-3626 took 146.54476308822632s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 9.179115295410156e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.3228137493133545s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.021457195281982422s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.504753112792969e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.1444091796875e-05s
INFO | --- Analysis for ISSN:_0080-3626 took 98.93799018859863s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 0.00017571449279785156s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 22.41126251220703s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.02161860466003418s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 4.267692565917969e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 1.239776611328125e-05s
INFO | --- Analysis for ISSN:_0080-3626. took 99.28949451446533s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.428246259689331s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 25.113431930541992s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.021941423416137695s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 9.322166442871094e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 1.0013580322265625e-05s
INFO | --- Analysis for istat-immigration took 151.36350917816162s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.12391424179077148s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 25.30056381225586s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.021647930145263672s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.528594970703125e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 1.5020370483398438e-05s
INFO | --- Analysis for it-aifa-drug-prices took 173.05984044075012s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.4299170970916748s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.34923315048217773s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.021375179290771484s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 8.320808410644531e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 1.2159347534179688e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 80.7100841999054s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 24.59048581123352s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.3044881820678711s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.021281719207763672s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 4.291534423828125e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 1.2874603271484375e-05s
INFO | --- Analysis for iucr-acta-cryst-e took 136.71303987503052s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 0.000152587890625s
Availability | VoID file availability check for IWMI Research Reports took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 23.082690238952637s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.02164769172668457s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 3.24249267578125e-05s
Believability | Calculation of trust value for IWMI Research Reports took 8.344650268554688e-06s
INFO | --- Analysis for iwmi-research-reports took 102.3344554901123s
Availability | SPARQL endpoint availability check for IWN took 0.00011897087097167969s
Availability | VoID file availability check for IWN took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for IWN took 0.3684251308441162s
Reputation | Calculation of the PageRank for IWN took 0.0221865177154541s
Interlinking | Calculation of Degree of Connection for IWN took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for IWN took 4.696846008300781e-05s
Believability | Calculation of trust value for IWN took 1.1920928955078125e-05s
INFO | --- Analysis for iwn took 103.30349802970886s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 0.03664708137512207s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.345367431640625s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.02124762535095215s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 3.933906555175781e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 1.3113021850585938e-05s
INFO | --- Analysis for j-global-knowledge took 104.47550630569458s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 4.220008850097656e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.0008878707885742188s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.5775601863861084s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.021197080612182617s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 4.124641418457031e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 1.239776611328125e-05s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 238.12222909927368s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 0.40807342529296875s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.3026549816131592s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.023054838180541992s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0008578300476074219s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 8.440017700195312e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 1.1920928955078125e-05s
INFO | --- Analysis for jamendo-dbtune took 26.898606300354004s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.363059997558594e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 1.1661560535430908s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.2890453338623047s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.021078824996948242s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for National Radioactivity Stat as Linked Data took 3.1996331214904785s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for japan-radioactivity-stat took 61.65442204475403s
Availability | SPARQL endpoint availability check for JEL Classification took 4.482269287109375e-05s
Availability | VoID file availability check for JEL Classification took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for JEL Classification took 25.531557083129883s
Reputation | Calculation of the PageRank for JEL Classification took 0.02124190330505371s
Interlinking | Calculation of Degree of Connection for JEL Classification took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.838539123535156e-05s
Believability | Calculation of trust value for JEL Classification took 1.430511474609375e-05s
INFO | --- Analysis for jel-classification took 109.74186491966248s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.18467116355896s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0006976127624511719s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 25.91900086402893s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.02153778076171875s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 4.57763671875e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 1.4781951904296875e-05s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 137.29053688049316s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 262.0172848701477s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0008480548858642578s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.32265424728393555s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.021676063537597656s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 8.487701416015625e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.239776611328125e-05s
INFO | --- Analysis for jita took 619.4791421890259s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 9.322166442871094e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 25.34167218208313s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.02222609519958496s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 3.886222839355469e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 1.1444091796875e-05s
INFO | --- Analysis for jmdict took 144.20900774002075s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.046337604522705s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0007398128509521484s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 20.744357347488403s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.021711349487304688s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0008339881896972656s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 0.00011086463928222656s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.4066696166992188e-05s
INFO | --- Analysis for john-goodwins-family-tree took 220.84764337539673s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 0.00011515617370605469s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 24.625423192977905s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.02115011215209961s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 4.553794860839844e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 1.2636184692382812e-05s
INFO | --- Analysis for jp-cos took 215.251118183136s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 9.1552734375e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0008223056793212891s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 23.16086435317993s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.02187514305114746s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 5.5789947509765625e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 1.1444091796875e-05s
INFO | --- Analysis for jp-textbook took 175.46552395820618s
Availability | SPARQL endpoint availability check for JRC-Names took 9.465217590332031e-05s
Availability | VoID file availability check for JRC-Names took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.31679344177246094s
Reputation | Calculation of the PageRank for JRC-Names took 0.022588014602661133s
Interlinking | Calculation of Degree of Connection for JRC-Names took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.552436828613281e-05s
Believability | Calculation of trust value for JRC-Names took 1.239776611328125e-05s
INFO | --- Analysis for jrc-names-ec took 78.43434381484985s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 0.8628015518188477s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 24.906904458999634s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.02213001251220703s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 8.106231689453125e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 1.239776611328125e-05s
INFO | --- Analysis for jrc-names-mlode took 93.8057963848114s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.839897155761719e-05s
Availability | VoID file availability check for JudaicaLink took 0.0007619857788085938s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.33117175102233887s
Reputation | Calculation of the PageRank for JudaicaLink took 0.021062850952148438s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00010943412780761719s
Believability | Calculation of trust value for JudaicaLink took 1.2874603271484375e-05s
INFO | --- Analysis for judaicalink took 59.95284628868103s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 6.103515625e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.00030040740966796875s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.30526232719421387s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.021055936813354492s
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.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 3.24249267578125e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 1.3589859008789062e-05s
INFO | --- Analysis for kaist-silver-standard-corpus took 80.70370078086853s
Availability | SPARQL endpoint availability check for KAKEN took 4.482269287109375e-05s
Availability | VoID file availability check for KAKEN took 0.0007519721984863281s
Completeness | Calculation of interlinking completeness for KAKEN took 25.93962788581848s
Reputation | Calculation of the PageRank for KAKEN took 0.021029233932495117s
Interlinking | Calculation of Degree of Connection for KAKEN took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for KAKEN took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for KAKEN took 3.743171691894531e-05s
Believability | Calculation of trust value for KAKEN took 1.2874603271484375e-05s
INFO | --- Analysis for kaken took 252.8447082042694s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.06900811195373535s
Availability | VoID file availability check for Kallikratis municipalities took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.300081729888916s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.021580219268798828s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 0.00011467933654785156s
Believability | Calculation of trust value for Kallikratis municipalities took 6.198883056640625e-06s
INFO | --- Analysis for kallikratis-municipalities took 52.48817539215088s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.982948303222656e-05s
Availability | VoID file availability check for Openflights Routes took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Openflights Routes took 25.900543451309204s
Reputation | Calculation of the PageRank for Openflights Routes took 0.0210573673248291s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.409385681152344e-05s
Believability | Calculation of trust value for Openflights Routes took 1.3113021850585938e-05s
INFO | --- Analysis for kasabi-openflights-routes took 99.8134377002716s
Availability | SPARQL endpoint availability check for EU Soccer League took 0.00016832351684570312s
Availability | VoID file availability check for EU Soccer League took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for EU Soccer League took 23.992676973342896s
Reputation | Calculation of the PageRank for EU Soccer League took 0.021523714065551758s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.552436828613281e-05s
Believability | Calculation of trust value for EU Soccer League took 2.0742416381835938e-05s
INFO | --- Analysis for KG:Course_Submission took 153.92812323570251s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 4.363059997558594e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 22.40437078475952s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.021255016326904297s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.7404556274414062e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 1.2159347534179688e-05s
INFO | --- Analysis for KING took 49.25506234169006s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.553794860839844e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0008780956268310547s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.2796156406402588s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020965099334716797s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 7.62939453125e-05s
Believability | Calculation of trust value for Klappstuhlclub took 9.298324584960938e-06s
INFO | --- Analysis for klappstuhlclub took 89.7993266582489s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 11.326917886734009s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.3324153423309326s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.02134227752685547s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.437301635742188e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 1.1682510375976562e-05s
INFO | --- Analysis for knoesis-linked-sensor-data took 141.27590489387512s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.4345855712890625e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.30161499977111816s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.021149396896362305s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.838539123535156e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.2159347534179688e-05s
INFO | --- Analysis for KnowledgeFusion took 77.4556200504303s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.4345855712890625e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0007951259613037109s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.3552286624908447s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.021117448806762695s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 7.200241088867188e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 2.0503997802734375e-05s
INFO | --- Analysis for kore-50-nif-ner-corpus took 139.43757009506226s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 0.00048041343688964844s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.3021860122680664s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.021407365798950195s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 4.267692565917969e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 1.1920928955078125e-05s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 57.782636642456055s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.846687316894531e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.32131147384643555s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0214383602142334s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.4332275390625e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.1920928955078125e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 146.21754813194275s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 9.036064147949219e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.29935145378112793s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.02106189727783203s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 3.552436828613281e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 1.2636184692382812e-05s
INFO | --- Analysis for ktr took 76.57793283462524s
Availability | SPARQL endpoint availability check for Informatics Studies took 9.226799011230469e-05s
Availability | VoID file availability check for Informatics Studies took 0.0007555484771728516s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.37509822845458984s
Reputation | Calculation of the PageRank for Informatics Studies took 0.021381855010986328s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 3.695487976074219e-05s
Believability | Calculation of trust value for Informatics Studies took 1.2636184692382812e-05s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 108.29029321670532s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.06867289543151855s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0007848739624023438s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.35439562797546387s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.021732091903686523s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 4.601478576660156e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 1.2636184692382812e-05s
INFO | --- Analysis for kupkb took 149.32012844085693s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 5.841255187988281e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.3517906665802002s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.021384716033935547s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0009968280792236328s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 5.888938903808594e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 1.33514404296875e-05s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 137.24668979644775s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 9.666504144668579s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0007700920104980469s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 26.537801265716553s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.021220922470092773s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 8.296966552734375e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 1.239776611328125e-05s
INFO | --- Analysis for l3s-dblp took 240.28991436958313s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 22.93910551071167s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 24.76469326019287s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.021166086196899414s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 8.058547973632812e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for lak-dataset took 212.87057518959045s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.20080327987670898s
Availability | VoID file availability check for  Language Name Authority List  took 0.0005345344543457031s
Extra | Recovery of all triples for  Language Name Authority List  took 234.1640284061432s
Performance | Total latancy measurement for  Language Name Authority List  took 0.5637476444244385s
Amount of data | Number of triples check for  Language Name Authority List  took 60.24005079269409s
Interoperability | New terms check for  Language Name Authority List  took 57.33364701271057s
Versatility | Languages check for  Language Name Authority List  took 300.09817123413086s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 58.63915395736694s
Security | Check HTTPS for  Language Name Authority List  took 0.32716917991638184s
Interpretability | RDF structures check for  Language Name Authority List  took 0.44591569900512695s
Versatility | Serialization formats check for  Language Name Authority List  took 4.9760658740997314s
Availability | RDF dump link check for  Language Name Authority List  took 0.2565741539001465s
License | MR license check for  Language Name Authority List  took 0.4114656448364258s
License | HR license check for  Language Name Authority List  took 291.5028612613678s
Amount of data | Number of property check for  Language Name Authority List  took 0.2091975212097168s
Understandability | Number of label check for  Language Name Authority List  took 3.1033613681793213s
Understandability | URI regex check for  Language Name Authority List  took 0.453399658203125s
Understandability | Vocabs check for  Language Name Authority List  took 0.0923147201538086s
Verifiability | Authors check for  Language Name Authority List  took 0.2788679599761963s
Verifiability | Publishers check for  Language Name Authority List  took 0.4421722888946533s
Performance | Throughput check for  Language Name Authority List  took 10.559712886810303s
Amount of data | Check the number of entities for  Language Name Authority List  took 7.557868957519531e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.21650385856628418s
Interlinking | sameAs chians check for  Language Name Authority List  took 6.335281133651733s
Interlinking | skos check for  Language Name Authority List  took 0.4370687007904053s
Interlinking | skos check for  Language Name Authority List  took 0.14035391807556152s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.5211026668548584s
Currency | Creation date check for  Language Name Authority List  took 0.4946746826171875s
Currency | Modification date check for  Language Name Authority List  took 0.265383243560791s
Rep.Conc. | URIs length for  Language Name Authority List  took 415.1203372478485s
Interoperability | New vocabularies check for  Language Name Authority List  took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.20409584045410156s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.38498926162719727s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.15354537963867188s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 39.91877722740173s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.222727060317993s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.6949350833892822s
Consistency | Disjoint class check for  Language Name Authority List  took 0.15215182304382324s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.429456949234s
Consistency | Misplaced classes for  Language Name Authority List  took 8.737390041351318s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 49.56002998352051s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.8524115085601807s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.54126048088074s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 3.100680112838745s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.5098583698272705s
Security | Sign check for  Language Name Authority List  took 0.1348438262939453s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 11.839410066604614s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 27.579926252365112s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.02176380157470703s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0008897781372070312s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 0.00011038780212402344s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.9073486328125e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.1682510375976562e-05s
INFO | --- Analysis for language-authority-list took 15007.723222255707s
Availability | SPARQL endpoint availability check for Lark took 384.3109872341156s
Availability | VoID file availability check for Lark took 0.0009906291961669922s
Completeness | Calculation of interlinking completeness for Lark took 0.5743749141693115s
Reputation | Calculation of the PageRank for Lark took 0.02175164222717285s
Interlinking | Calculation of Degree of Connection for Lark took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Lark took 8.988380432128906e-05s
Believability | Calculation of trust value for Lark took 1.2159347534179688e-05s
INFO | --- Analysis for LARK took 1789.8859376907349s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.5296387672424316s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.28602170944213867s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.022153139114379883s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 5.459785461425781e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for LASLA took 102.10908246040344s
Availability | SPARQL endpoint availability check for LATC Linksets took 4.887580871582031e-05s
Availability | VoID file availability check for LATC Linksets took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for LATC Linksets took 24.639430046081543s
Reputation | Calculation of the PageRank for LATC Linksets took 0.021329402923583984s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 3.552436828613281e-05s
Believability | Calculation of trust value for LATC Linksets took 8.106231689453125e-06s
INFO | --- Analysis for latc-linksets took 164.80760836601257s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.46216797828674316s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0007014274597167969s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 25.51562237739563s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.021577835083007812s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 5.459785461425781e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 1.2636184692382812e-05s
INFO | --- Analysis for Latin_Vallex2.0 took 130.99614310264587s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.46866774559020996s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 24.00716781616211s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.021912574768066406s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 4.00543212890625e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 1.2636184692382812e-05s
INFO | --- Analysis for LatinAffectus took 154.6936137676239s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.4684715270996094s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.36841297149658203s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.02112746238708496s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 5.2928924560546875e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for LatinWordnetLiLa took 86.23492956161499s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.5299530029296875e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 29.497380256652832s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.021151304244995117s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.0001392364501953125s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.2159347534179688e-05s
INFO | --- Analysis for lcsh took 85.94396829605103s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 0.00016236305236816406s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0007545948028564453s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 25.30904459953308s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.021112918853759766s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.869171142578125e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 1.2874603271484375e-05s
INFO | --- Analysis for lcsubjects took 82.49549293518066s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.854067087173462s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0007870197296142578s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.32069993019104004s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.021343469619750977s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.9591064453125e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.3828277587890625e-05s
INFO | --- Analysis for ldt@library took 88.11335515975952s
Availability | SPARQL endpoint availability check for U ime Legije took 4.601478576660156e-05s
Availability | VoID file availability check for U ime Legije took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for U ime Legije took 26.858521223068237s
Reputation | Calculation of the PageRank for U ime Legije took 0.021342754364013672s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 4.3392181396484375e-05s
Believability | Calculation of trust value for U ime Legije took 1.1444091796875e-05s
INFO | --- Analysis for LEGIJA_STRANACA took 164.00275039672852s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 0.13912010192871094s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.3028237819671631s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.021202564239501953s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 3.552436828613281e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 1.1205673217773438e-05s
INFO | --- Analysis for legislation-openuplabs took 131.6817684173584s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.46836042404174805s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.3382079601287842s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.02115321159362793s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.677078247070312e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.1444091796875e-05s
INFO | --- Analysis for LemmaBank took 110.7955117225647s
Availability | SPARQL endpoint availability check for lemonUby took 4.839897155761719e-05s
Availability | VoID file availability check for lemonUby took 0.0007507801055908203s
Completeness | Calculation of interlinking completeness for lemonUby took 0.33175158500671387s
Reputation | Calculation of the PageRank for lemonUby took 0.021065473556518555s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for lemonUby took 7.486343383789062e-05s
Believability | Calculation of trust value for lemonUby took 1.2159347534179688e-05s
INFO | --- Analysis for lemonuby took 154.38746857643127s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.458427429199219e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 27.449859142303467s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.02121138572692871s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 4.363059997558594e-05s
Believability | Calculation of trust value for LemonWiktionary took 8.58306884765625e-06s
INFO | --- Analysis for lemonwiktionary took 56.20033121109009s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.44612908363342285s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 23.274104118347168s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02141261100769043s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 4.601478576660156e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 1.7404556274414062e-05s
INFO | --- Analysis for LewisShort took 105.15625047683716s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.0195305347442627s
Availability | VoID file availability check for LEXIN-RDF took 0.0007321834564208984s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 25.225462436676025s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.02135181427001953s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.838539123535156e-05s
Believability | Calculation of trust value for LEXIN-RDF took 1.239776611328125e-05s
INFO | --- Analysis for lexin-rdf took 162.48740124702454s
Availability | SPARQL endpoint availability check for lexinfo took 4.57763671875e-05s
Availability | VoID file availability check for lexinfo took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for lexinfo took 0.3752326965332031s
Reputation | Calculation of the PageRank for lexinfo took 0.02197122573852539s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for lexinfo took 9.799003601074219e-05s
Believability | Calculation of trust value for lexinfo took 1.430511474609375e-05s
INFO | --- Analysis for lexinfo took 80.24757766723633s
Availability | SPARQL endpoint availability check for Lexvo took 5.3882598876953125e-05s
Availability | VoID file availability check for Lexvo took 0.16305947303771973s
Completeness | Calculation of interlinking completeness for Lexvo took 0.31189441680908203s
Reputation | Calculation of the PageRank for Lexvo took 0.0209348201751709s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00020837783813476562s
Interoperability | Check the re-using of existing vocabs for Lexvo took 1.0678927898406982s
Believability | Calculation of trust value for Lexvo took 1.239776611328125e-05s
INFO | --- Analysis for lexvo took 105.30096316337585s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.887580871582031e-05s
Availability | VoID file availability check for Lexvo.org took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Lexvo.org took 26.294579029083252s
Reputation | Calculation of the PageRank for Lexvo.org took 0.02127361297607422s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 8.368492126464844e-05s
Believability | Calculation of trust value for Lexvo.org took 1.239776611328125e-05s
INFO | --- Analysis for lexvo-org took 103.068683385849s
Availability | SPARQL endpoint availability check for LIBRIS took 0.38026952743530273s
Availability | VoID file availability check for LIBRIS took 0.0008139610290527344s
Extra | Recovery of all triples for LIBRIS took 6.301254034042358s
Performance | Total latancy measurement for LIBRIS took 0.7382805347442627s
Amount of data | Number of triples check for LIBRIS took 26.20703387260437s
Interoperability | New terms check for LIBRIS took 18.217640161514282s
Versatility | Languages check for LIBRIS took 0.18435168266296387s
Interpretability | Number of blank nodes check for LIBRIS took 300.09734749794006s
Security | Check HTTPS for LIBRIS took 0.34677743911743164s
Interpretability | RDF structures check for LIBRIS took 0.250652551651001s
Versatility | Serialization formats check for LIBRIS took 0.22687196731567383s
Availability | RDF dump link check for LIBRIS took 0.1301898956298828s
License | MR license check for LIBRIS took 0.18816280364990234s
License | HR license check for LIBRIS took 0.16805338859558105s
Amount of data | Number of property check for LIBRIS took 0.19983696937561035s
Understandability | Number of label check for LIBRIS took 0.31009817123413086s
Understandability | URI regex check for LIBRIS took 0.25991106033325195s
Understandability | Vocabs check for LIBRIS took 0.1400766372680664s
Verifiability | Authors check for LIBRIS took 0.14915680885314941s
Verifiability | Publishers check for LIBRIS took 0.15307259559631348s
Performance | Throughput check for LIBRIS took 10.7867112159729s
Amount of data | Check the number of entities for LIBRIS took 7.557868957519531e-05s
Verifiability | Contribs. check for LIBRIS took 0.16598200798034668s
Interlinking | sameAs chians check for LIBRIS took 0.16698145866394043s
Interlinking | skos check for LIBRIS took 0.16692686080932617s
Interlinking | skos check for LIBRIS took 0.14167284965515137s
Timeliness | dataset update frequency check for LIBRIS took 0.14124703407287598s
Currency | Creation date check for LIBRIS took 0.36984944343566895s
Currency | Modification date check for LIBRIS took 0.6286330223083496s
Rep.Conc. | URIs length for LIBRIS took 95.143301486969s
Interoperability | New vocabularies check for LIBRIS took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.18344354629516602s
Accuracy | Check Functional Property for LIBRIS took 0.18474626541137695s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.15368056297302246s
Accuracy | Check Datatype consistency for LIBRIS took 0.29641246795654297s
Consistency | Disjoint class check for LIBRIS took 0.17746877670288086s
Consistency | Check Misplaced properties for LIBRIS took 71.08974885940552s
Consistency | Misplaced classes for LIBRIS took 1.1760573387145996s
Consistency | Check Ontology hijacking for LIBRIS took 3.5558536052703857s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.3681871891021729s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 71.82409572601318s
Conciseness | Check Extensional conciseness for LIBRIS took 0.29180240631103516s
Conciseness | Check Intensional conciseness for LIBRIS took 0.4188680648803711s
Security | Sign check for LIBRIS took 0.1971433162689209s
Availability | Check URIs Dereferenciability for LIBRIS took 8.6389741897583s
Completeness | Calculation of interlinking completeness for LIBRIS took 22.358710527420044s
Reputation | Calculation of the PageRank for LIBRIS took 0.020946264266967773s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 0.00010395050048828125s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.430511474609375e-06s
Believability | Calculation of trust value for LIBRIS took 1.2159347534179688e-05s
INFO | --- Analysis for libris took 1215.531522512436s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.08893799781799316s
Availability | VoID file availability check for Public Library of Veroia took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 28.693760871887207s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.02202296257019043s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 8.821487426757812e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.2636184692382812e-05s
INFO | --- Analysis for libver took 133.2225058078766s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.13407659530639648s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 24.59234070777893s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.0214078426361084s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 9.417533874511719e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 1.0013580322265625e-05s
INFO | --- Analysis for lichfield-spending took 123.09200763702393s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 9.942054748535156e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.29169321060180664s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.024216651916503906s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 4.2438507080078125e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.3113021850585938e-05s
INFO | --- Analysis for lime took 75.6436357498169s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.553794860839844e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.48505115509033203s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.3253018856048584s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.02269577980041504s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0008435249328613281s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00012111663818359375s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.239776611328125e-05s
INFO | --- Analysis for lingvoj took 105.95037293434143s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 6.818771362304688e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0003464221954345703s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.3251461982727051s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.022524118423461914s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 0.00011539459228515625s
Believability | Calculation of trust value for Linked Crunchbase took 1.1920928955078125e-05s
INFO | --- Analysis for linked-crunchbase took 90.20215725898743s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1880712509155273s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.3156449794769287s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.022335290908813477s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 8.416175842285156e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.430511474609375e-05s
INFO | --- Analysis for linked-drugs took 55.80116391181946s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 8.153915405273438e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.41617846488952637s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.023020505905151367s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0008101463317871094s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 0.0001304149627685547s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 1.1205673217773438e-05s
INFO | --- Analysis for linked-edgar took 127.99531865119934s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 8.797645568847656e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 24.485631704330444s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.02114391326904297s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 0.00010228157043457031s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 1.1682510375976562e-05s
INFO | --- Analysis for linked-eurostat took 123.22058629989624s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.792213439941406e-05s
Availability | VoID file availability check for linked hypernyms took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.3060176372528076s
Reputation | Calculation of the PageRank for linked hypernyms took 0.02202892303466797s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 8.0108642578125e-05s
Believability | Calculation of trust value for linked hypernyms took 1.2636184692382812e-05s
INFO | --- Analysis for linked-hypernyms took 74.92890071868896s
Availability | SPARQL endpoint availability check for Linked Life Data took 208.42318987846375s
Availability | VoID file availability check for Linked Life Data took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Linked Life Data took 32.010170221328735s
Reputation | Calculation of the PageRank for Linked Life Data took 0.02139115333557129s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 6.008148193359375e-05s
Believability | Calculation of trust value for Linked Life Data took 2.3365020751953125e-05s
INFO | --- Analysis for linked-life-data took 1043.3326420783997s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.24683189392089844s
Availability | VoID file availability check for Linked Logainm took 0.0006725788116455078s
Extra | Recovery of all triples for Linked Logainm took 2.245089292526245s
Performance | Total latancy measurement for Linked Logainm took 0.5665946006774902s
Amount of data | Number of triples check for Linked Logainm took 0.24873590469360352s
Interoperability | New terms check for Linked Logainm took 1.5396678447723389s
Versatility | Languages check for Linked Logainm took 1.4770381450653076s
Interpretability | Number of blank nodes check for Linked Logainm took 0.1879887580871582s
Security | Check HTTPS for Linked Logainm took 0.2589893341064453s
Interpretability | RDF structures check for Linked Logainm took 0.3946969509124756s
Versatility | Serialization formats check for Linked Logainm took 0.16704988479614258s
Availability | RDF dump link check for Linked Logainm took 0.11803960800170898s
License | MR license check for Linked Logainm took 0.11130094528198242s
License | HR license check for Linked Logainm took 0.11689209938049316s
Amount of data | Number of property check for Linked Logainm took 0.14956235885620117s
Understandability | Number of label check for Linked Logainm took 0.19226694107055664s
Understandability | URI regex check for Linked Logainm took 0.3954460620880127s
Understandability | Vocabs check for Linked Logainm took 0.11319279670715332s
Verifiability | Authors check for Linked Logainm took 0.11657476425170898s
Verifiability | Publishers check for Linked Logainm took 0.11330842971801758s
Performance | Throughput check for Linked Logainm took 10.506141662597656s
Amount of data | Check the number of entities for Linked Logainm took 8.821487426757812e-05s
Verifiability | Contribs. check for Linked Logainm took 0.10854101181030273s
Interlinking | sameAs chians check for Linked Logainm took 0.13701891899108887s
Interlinking | skos check for Linked Logainm took 0.14407014846801758s
Interlinking | skos check for Linked Logainm took 0.12341761589050293s
Timeliness | dataset update frequency check for Linked Logainm took 0.11635470390319824s
Currency | Creation date check for Linked Logainm took 0.290560245513916s
Currency | Modification date check for Linked Logainm took 0.2639310359954834s
Rep.Conc. | URIs length for Linked Logainm took 0.9646832942962646s
Interoperability | New vocabularies check for Linked Logainm took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.1312258243560791s
Accuracy | Check Functional Property for Linked Logainm took 0.23008465766906738s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.19537901878356934s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.6344864368438721s
Accuracy | Check White space in annotation for Linked Logainm took 0.0246429443359375s
Accuracy | Check Datatype consistency for Linked Logainm took 0.029776811599731445s
Consistency | Disjoint class check for Linked Logainm took 0.19106435775756836s
Consistency | Check Misplaced properties for Linked Logainm took 0.33681273460388184s
Consistency | Misplaced classes for Linked Logainm took 0.2977614402770996s
Consistency | Check Ontology hijacking for Linked Logainm took 1.9330260753631592s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.361387014389038s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.5633342266082764s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.03274202346801758s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.21004867553710938s
Security | Sign check for Linked Logainm took 0.12392950057983398s
Availability | Check URIs Dereferenciability for Linked Logainm took 988.6906237602234s
Completeness | Calculation of interlinking completeness for Linked Logainm took 27.350173711776733s
Reputation | Calculation of the PageRank for Linked Logainm took 0.023080825805664062s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0009059906005859375s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 9.751319885253906e-05s
Interoperability | Check the re-using of existing vocabs for Linked Logainm took 1.9073486328125e-06s
Believability | Calculation of trust value for Linked Logainm took 1.33514404296875e-05s
INFO | --- Analysis for linked-logainm took 1250.933867931366s
Availability | SPARQL endpoint availability check for Linked NUTS took 8.96453857421875e-05s
Availability | VoID file availability check for Linked NUTS took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Linked NUTS took 29.516958713531494s
Reputation | Calculation of the PageRank for Linked NUTS took 0.021748065948486328s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 6.222724914550781e-05s
Believability | Calculation of trust value for Linked NUTS took 9.059906005859375e-06s
INFO | --- Analysis for linked-nuts took 128.46700716018677s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 0.0005042552947998047s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.302562952041626s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.021317481994628906s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 4.029273986816406e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 7.62939453125e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 155.36752605438232s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.6332247257232666s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0003178119659423828s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 30.281461000442505s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.02140331268310547s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 4.363059997558594e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 9.298324584960938e-06s
INFO | --- Analysis for linked-open-camera took 107.8420763015747s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 3.9196088314056396s
Availability | VoID file availability check for Linked Open Commerce took 0.0007975101470947266s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 22.997219800949097s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.021113872528076172s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0008063316345214844s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 4.124641418457031e-05s
Believability | Calculation of trust value for Linked Open Commerce took 1.2636184692382812e-05s
INFO | --- Analysis for linked-open-commerce took 114.14527773857117s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 0.3744654655456543s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 24.865444660186768s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.021234750747680664s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010919570922851562s
Believability | Calculation of trust value for Linked Open Data of Ecology took 8.344650268554688e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 76.96589016914368s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 6.699562072753906e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 23.251006364822388s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.021433353424072266s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 0.00010514259338378906s
Believability | Calculation of trust value for Linked Open Numbers took 9.775161743164062e-06s
INFO | --- Analysis for linked-open-numbers took 140.4365692138672s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 9.131431579589844e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 27.984540224075317s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.021077394485473633s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 3.6716461181640625e-05s
Believability | Calculation of trust value for Linked Open Piracy took 5.0067901611328125e-06s
INFO | --- Analysis for linked-open-piracy took 154.66157221794128s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 2.147343158721924s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 19.80432915687561s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.021371841430664062s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0008003711700439453s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 4.0531158447265625e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 1.8596649169921875e-05s
INFO | --- Analysis for linked-open-senate took 154.65599489212036s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 11.183118104934692s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0006918907165527344s
Extra | Recovery of all triples for Linked Open Vocabularies (LOV) took 69.02899837493896s
Performance | Total latancy measurement for Linked Open Vocabularies (LOV) took 1.3736872673034668s
Amount of data | Number of triples check for Linked Open Vocabularies (LOV) took 1.824930191040039s
Interoperability | New terms check for Linked Open Vocabularies (LOV) took 2.242051601409912s
Versatility | Languages check for Linked Open Vocabularies (LOV) took 13.05373477935791s
Interpretability | Number of blank nodes check for Linked Open Vocabularies (LOV) took 1.8276686668395996s
Interpretability | RDF structures check for Linked Open Vocabularies (LOV) took 0.21370458602905273s
Versatility | Serialization formats check for Linked Open Vocabularies (LOV) took 0.22419261932373047s
Availability | RDF dump link check for Linked Open Vocabularies (LOV) took 0.9708197116851807s
License | MR license check for Linked Open Vocabularies (LOV) took 0.18662691116333008s
License | HR license check for Linked Open Vocabularies (LOV) took 46.39906859397888s
Amount of data | Number of property check for Linked Open Vocabularies (LOV) took 0.21988296508789062s
Understandability | Number of label check for Linked Open Vocabularies (LOV) took 0.8357629776000977s
Understandability | URI regex check for Linked Open Vocabularies (LOV) took 1.0325815677642822s
Understandability | Vocabs check for Linked Open Vocabularies (LOV) took 0.43306422233581543s
Verifiability | Authors check for Linked Open Vocabularies (LOV) took 0.6462192535400391s
Verifiability | Publishers check for Linked Open Vocabularies (LOV) took 0.21662378311157227s
Performance | Throughput check for Linked Open Vocabularies (LOV) took 12.118226051330566s
Amount of data | Check the number of entities for Linked Open Vocabularies (LOV) took 1.1291959285736084s
Verifiability | Contribs. check for Linked Open Vocabularies (LOV) took 0.36084747314453125s
Interlinking | sameAs chians check for Linked Open Vocabularies (LOV) took 0.42013072967529297s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.18282079696655273s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.23423099517822266s
Timeliness | dataset update frequency check for Linked Open Vocabularies (LOV) took 0.326610803604126s
Currency | Creation date check for Linked Open Vocabularies (LOV) took 1.7277133464813232s
Currency | Modification date check for Linked Open Vocabularies (LOV) took 0.6248681545257568s
Rep.Conc. | URIs length for Linked Open Vocabularies (LOV) took 24.092280864715576s
Interoperability | New vocabularies check for Linked Open Vocabularies (LOV) took 19.8265323638916s
Consistency | Deprecated classes/propertiers check for Linked Open Vocabularies (LOV) took 0.29688501358032227s
Accuracy | Check Functional Property for Linked Open Vocabularies (LOV) took 0.2108747959136963s
Accuracy | Check Inverse Functional Property for Linked Open Vocabularies (LOV) took 0.5092668533325195s
Accuracy | Check Empty annotation labels for Linked Open Vocabularies (LOV) took 7.02916145324707s
Accuracy | Check White space in annotation for Linked Open Vocabularies (LOV) took 0.6941244602203369s
Accuracy | Check Datatype consistency for Linked Open Vocabularies (LOV) took 4.878955841064453s
Consistency | Disjoint class check for Linked Open Vocabularies (LOV) took 0.24062871932983398s
Consistency | Check Misplaced properties for Linked Open Vocabularies (LOV) took 6.497201442718506s
Consistency | Misplaced classes for Linked Open Vocabularies (LOV) took 0.18317604064941406s
Consistency | Check Ontology hijacking for Linked Open Vocabularies (LOV) took 5.838082551956177s
Consistency | Check Invalid usage of undefined classes for Linked Open Vocabularies (LOV) took 1.4804508686065674s
Conciseness | Check Extensional conciseness for Linked Open Vocabularies (LOV) took 2.921342372894287s
Conciseness | Check Intensional conciseness for Linked Open Vocabularies (LOV) took 2.2124390602111816s
Security | Sign check for Linked Open Vocabularies (LOV) took 0.4487626552581787s
Availability | Check URIs Dereferenciability for Linked Open Vocabularies (LOV) took 5729.699016094208s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 21.27158832550049s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.02192997932434082s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for Linked Open Vocabularies (LOV) took 19.155991315841675s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.1682510375976562e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 6880.124964237213s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 5.936622619628906e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 26.064424753189087s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.02108621597290039s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 7.128715515136719e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 2.0742416381835938e-05s
INFO | --- Analysis for linked-periodicals took 152.55562496185303s
Availability | SPARQL endpoint availability check for Linked Index took 9.059906005859375e-05s
Availability | VoID file availability check for Linked Index took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for Linked Index took 25.059174299240112s
Reputation | Calculation of the PageRank for Linked Index took 0.023325443267822266s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.7738037109375e-05s
Believability | Calculation of trust value for Linked Index took 1.2636184692382812e-05s
INFO | --- Analysis for linked-stockindex took 100.13992357254028s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.930269718170166s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 22.934224128723145s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.021740198135375977s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 5.269050598144531e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.2636184692382812e-05s
INFO | --- Analysis for linked-structured-product-labels took 128.38708233833313s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.048990488052368164s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 22.07352089881897s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.023232221603393555s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 5.1021575927734375e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 1.2159347534179688e-05s
INFO | --- Analysis for linked-taiwan-geo-names took 165.21285128593445s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.263729572296143s
Availability | VoID file availability check for Linked TCGA took 0.0008146762847900391s
Completeness | Calculation of interlinking completeness for Linked TCGA took 27.980477333068848s
Reputation | Calculation of the PageRank for Linked TCGA took 0.0216217041015625s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 9.918212890625e-05s
Believability | Calculation of trust value for Linked TCGA took 1.239776611328125e-05s
INFO | --- Analysis for linked-tcga took 238.89926719665527s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.10391497611999512s
Availability | VoID file availability check for Linked User Feedback took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.31173062324523926s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.021285295486450195s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 4.267692565917969e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.5974044799804688e-05s
INFO | --- Analysis for linked-user-feedback took 94.15418887138367s
Availability | SPARQL endpoint availability check for USPTO Patent data took 9.179115295410156e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0008389949798583984s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.3697624206542969s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.02464747428894043s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0008828639984130859s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 0.00011563301086425781s
Believability | Calculation of trust value for USPTO Patent data took 1.33514404296875e-05s
INFO | --- Analysis for linked-uspto-patent-data took 147.12168645858765s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 0.03921079635620117s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.2953050136566162s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.02114129066467285s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 4.553794860839844e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 1.33514404296875e-05s
INFO | --- Analysis for linkedarc took 74.05623817443848s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.20798993110656738s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.29055237770080566s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.02151799201965332s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 4.4345855712890625e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.3828277587890625e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 167.82023191452026s
Availability | SPARQL endpoint availability check for LinkedCT took 2.024243116378784s
Availability | VoID file availability check for LinkedCT took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for LinkedCT took 23.11847496032715s
Reputation | Calculation of the PageRank for LinkedCT took 0.021394014358520508s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.0001049041748046875s
Believability | Calculation of trust value for LinkedCT took 1.3113021850585938e-05s
INFO | --- Analysis for linkedct took 182.7199409008026s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.29088878631591797s
Availability | VoID file availability check for LinkedGeoData took 0.0004754066467285156s
Extra | Recovery of all triples for LinkedGeoData took 7.0986902713775635s
Performance | Total latancy measurement for LinkedGeoData took 0.6573646068572998s
Amount of data | Number of triples check for LinkedGeoData took 51.40818452835083s
Interoperability | New terms check for LinkedGeoData took 91.1608202457428s
Versatility | Languages check for LinkedGeoData took 180.37321877479553s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.22124719619750977s
Security | Check HTTPS for LinkedGeoData took 0.30712008476257324s
Interpretability | RDF structures check for LinkedGeoData took 0.9263515472412109s
Versatility | Serialization formats check for LinkedGeoData took 0.3558013439178467s
Availability | RDF dump link check for LinkedGeoData took 0.1636965274810791s
License | MR license check for LinkedGeoData took 0.6756715774536133s
License | HR license check for LinkedGeoData took 116.41361951828003s
Amount of data | Number of property check for LinkedGeoData took 0.18685626983642578s
Understandability | Number of label check for LinkedGeoData took 2.2821433544158936s
Understandability | URI regex check for LinkedGeoData took 0.3924736976623535s
Understandability | Vocabs check for LinkedGeoData took 0.1859116554260254s
Verifiability | Authors check for LinkedGeoData took 0.15821099281311035s
Verifiability | Publishers check for LinkedGeoData took 0.13454866409301758s
Performance | Throughput check for LinkedGeoData took 10.478907108306885s
Amount of data | Check the number of entities for LinkedGeoData took 0.06913113594055176s
Verifiability | Contribs. check for LinkedGeoData took 2.160579204559326s
Interlinking | sameAs chians check for LinkedGeoData took 0.30882859230041504s
Interlinking | skos check for LinkedGeoData took 0.4237644672393799s
Interlinking | skos check for LinkedGeoData took 0.1208951473236084s
Timeliness | dataset update frequency check for LinkedGeoData took 0.37550973892211914s
Currency | Creation date check for LinkedGeoData took 0.49876999855041504s
Currency | Modification date check for LinkedGeoData took 0.28137898445129395s
Rep.Conc. | URIs length for LinkedGeoData took 271.1389696598053s
Interoperability | New vocabularies check for LinkedGeoData took 27.096132040023804s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.16146612167358398s
Accuracy | Check Functional Property for LinkedGeoData took 0.2205655574798584s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.18103623390197754s
Accuracy | Check Empty annotation labels for LinkedGeoData took 1.66621732711792s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15897560119628906s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.14043617248535156s
Consistency | Disjoint class check for LinkedGeoData took 0.25950169563293457s
Consistency | Check Misplaced properties for LinkedGeoData took 181.12479448318481s
Consistency | Misplaced classes for LinkedGeoData took 0.659569501876831s
Consistency | Check Ontology hijacking for LinkedGeoData took 3.817721366882324s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.363771677017212s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 182.03229880332947s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.15044498443603516s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.3651621341705322s
Security | Sign check for LinkedGeoData took 0.7762620449066162s
Availability | Check URIs Dereferenciability for LinkedGeoData took 11.121596336364746s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 1.044050931930542s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.021570444107055664s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.0001361370086669922s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 16.875692129135132s
Believability | Calculation of trust value for LinkedGeoData took 8.344650268554688e-06s
INFO | --- Analysis for linkedgeodata took 2316.8743512630463s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 0.2533683776855469s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.0006663799285888672s
Extra | Recovery of all triples for LinkedGeoData: Aerodromes took 7.091406583786011s
Performance | Total latancy measurement for LinkedGeoData: Aerodromes took 0.6580753326416016s
Amount of data | Number of triples check for LinkedGeoData: Aerodromes took 48.44734025001526s
Interoperability | New terms check for LinkedGeoData: Aerodromes took 91.27455759048462s
Versatility | Languages check for LinkedGeoData: Aerodromes took 181.19658613204956s
Interpretability | Number of blank nodes check for LinkedGeoData: Aerodromes took 0.21376466751098633s
Security | Check HTTPS for LinkedGeoData: Aerodromes took 0.31951117515563965s
Interpretability | RDF structures check for LinkedGeoData: Aerodromes took 0.1546492576599121s
Versatility | Serialization formats check for LinkedGeoData: Aerodromes took 0.16867756843566895s
Availability | RDF dump link check for LinkedGeoData: Aerodromes took 0.12841176986694336s
License | MR license check for LinkedGeoData: Aerodromes took 0.12157297134399414s
License | HR license check for LinkedGeoData: Aerodromes took 117.40355134010315s
Amount of data | Number of property check for LinkedGeoData: Aerodromes took 0.16454148292541504s
Understandability | Number of label check for LinkedGeoData: Aerodromes took 1.0831010341644287s
Understandability | URI regex check for LinkedGeoData: Aerodromes took 0.2825124263763428s
Understandability | Vocabs check for LinkedGeoData: Aerodromes took 0.17627620697021484s
Verifiability | Authors check for LinkedGeoData: Aerodromes took 0.1334822177886963s
Verifiability | Publishers check for LinkedGeoData: Aerodromes took 0.13069438934326172s
Performance | Throughput check for LinkedGeoData: Aerodromes took 10.441293716430664s
Amount of data | Check the number of entities for LinkedGeoData: Aerodromes took 0.07558727264404297s
Verifiability | Contribs. check for LinkedGeoData: Aerodromes took 0.16342401504516602s
Interlinking | sameAs chians check for LinkedGeoData: Aerodromes took 0.20358991622924805s
Interlinking | skos check for LinkedGeoData: Aerodromes took 0.15799307823181152s
Interlinking | skos check for LinkedGeoData: Aerodromes took 0.12717199325561523s
Timeliness | dataset update frequency check for LinkedGeoData: Aerodromes took 0.12583112716674805s
Currency | Creation date check for LinkedGeoData: Aerodromes took 0.2801778316497803s
Currency | Modification date check for LinkedGeoData: Aerodromes took 0.28428173065185547s
Rep.Conc. | URIs length for LinkedGeoData: Aerodromes took 273.1977872848511s
Interoperability | New vocabularies check for LinkedGeoData: Aerodromes took 15.820497751235962s
Consistency | Deprecated classes/propertiers check for LinkedGeoData: Aerodromes took 0.16454529762268066s
Accuracy | Check Functional Property for LinkedGeoData: Aerodromes took 0.16216349601745605s
Accuracy | Check Inverse Functional Property for LinkedGeoData: Aerodromes took 0.13313031196594238s
Accuracy | Check Empty annotation labels for LinkedGeoData: Aerodromes took 1.9206318855285645s
Accuracy | Check White space in annotation for LinkedGeoData: Aerodromes took 0.16019201278686523s
Accuracy | Check Datatype consistency for LinkedGeoData: Aerodromes took 0.14382505416870117s
Consistency | Disjoint class check for LinkedGeoData: Aerodromes took 0.13302302360534668s
Consistency | Check Misplaced properties for LinkedGeoData: Aerodromes took 182.0757191181183s
Consistency | Misplaced classes for LinkedGeoData: Aerodromes took 0.6376304626464844s
Consistency | Check Ontology hijacking for LinkedGeoData: Aerodromes took 3.8125498294830322s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData: Aerodromes took 1.378633737564087s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData: Aerodromes took 181.750958442688s
Conciseness | Check Extensional conciseness for LinkedGeoData: Aerodromes took 0.15274572372436523s
Conciseness | Check Intensional conciseness for LinkedGeoData: Aerodromes took 0.32752513885498047s
Security | Sign check for LinkedGeoData: Aerodromes took 0.1680772304534912s
Availability | Check URIs Dereferenciability for LinkedGeoData: Aerodromes took 10.25633692741394s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.5883004665374756s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.022024869918823242s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 4.076957702636719e-05s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData: Aerodromes took 13.94869065284729s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 1.9073486328125e-05s
INFO | --- Analysis for linkedgeodata-aerodromes took 2121.25962638855s
Availability | SPARQL endpoint availability check for LinkedLCCN took 10.680105924606323s
Availability | VoID file availability check for LinkedLCCN took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.3030548095703125s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.021693944931030273s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00011157989501953125s
Believability | Calculation of trust value for LinkedLCCN took 1.2874603271484375e-05s
INFO | --- Analysis for linkedlccn took 164.77065777778625s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.3392181396484375e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.3495814800262451s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.022225379943847656s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0008051395416259766s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 5.030632019042969e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.33514404296875e-05s
INFO | --- Analysis for linkedmarkmail took 112.56940460205078s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 2.902205228805542s
Availability | VoID file availability check for Linked Movie DataBase took 0.0008280277252197266s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.3278682231903076s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.021365880966186523s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00013375282287597656s
Believability | Calculation of trust value for Linked Movie DataBase took 8.821487426757812e-06s
INFO | --- Analysis for linkedmdb took 122.47887086868286s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.6728827953338623s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 27.200810432434082s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.02166748046875s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 8.106231689453125e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 1.1444091796875e-05s
INFO | --- Analysis for linkedspending took 108.9550850391388s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.06910538673400879s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 24.086458683013916s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.02109241485595703s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00011467933654785156s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.1682510375976562e-05s
INFO | --- Analysis for linklion took 164.93225073814392s
Availability | SPARQL endpoint availability check for Lion's Den took 4.3392181396484375e-05s
Availability | VoID file availability check for Lion's Den took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.2990870475769043s
Reputation | Calculation of the PageRank for Lion's Den took 0.021117687225341797s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 3.457069396972656e-05s
Believability | Calculation of trust value for Lion's Den took 1.3113021850585938e-05s
INFO | --- Analysis for lionsden took 100.59523463249207s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 600.3820757865906s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 25.206783294677734s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.021338701248168945s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.91278076171875e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 1.33514404296875e-05s
INFO | --- Analysis for lista-encabezamientos-materia took 1338.835461616516s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.0482134819030762s
Availability | VoID file availability check for lobid-organisations took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.29908132553100586s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02148127555847168s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 0.00012373924255371094s
Believability | Calculation of trust value for lobid-organisations took 1.2874603271484375e-05s
INFO | --- Analysis for lobid-organisations took 122.9796929359436s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.7632136344909668s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.37207603454589844s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.022955894470214844s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0008711814880371094s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00011754035949707031s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 1.2636184692382812e-05s
INFO | --- Analysis for lobid-resources took 87.85288977622986s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.4345855712890625e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 23.8317928314209s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.021120548248291016s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 8.20159912109375e-05s
Believability | Calculation of trust value for Linked Open Colors took 1.3113021850585938e-05s
INFO | --- Analysis for loc took 158.40758609771729s
Availability | SPARQL endpoint availability check for Location Ontology took 0.00010132789611816406s
Availability | VoID file availability check for Location Ontology took 0.0004050731658935547s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.3204982280731201s
Reputation | Calculation of the PageRank for Location Ontology took 0.021256685256958008s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.62396240234375e-05s
Believability | Calculation of trust value for Location Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for Location_Ontology took 75.52502703666687s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 0.00010180473327636719s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 21.7042977809906s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.021184682846069336s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 4.220008850097656e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 1.3589859008789062e-05s
INFO | --- Analysis for locv took 220.33184790611267s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7998752593994141s
Availability | VoID file availability check for LOD-a-lot took 0.0008983612060546875s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 22.63852071762085s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.02137613296508789s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 4.029273986816406e-05s
Believability | Calculation of trust value for LOD-a-lot took 1.33514404296875e-05s
INFO | --- Analysis for lod-a-lot took 222.5757131576538s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 0.00011110305786132812s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 20.848480224609375s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.02224874496459961s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 4.172325134277344e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 1.2874603271484375e-05s
INFO | --- Analysis for lod-it_scuole-italiane took 136.1388385295868s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.506111145019531e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 23.093355178833008s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.021572351455688477s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 9.918212890625e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 1.1444091796875e-05s
INFO | --- Analysis for lod2-project-wiki took 122.15194821357727s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.7677226066589355s
Availability | VoID file availability check for LODAC BDLS took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 24.35703682899475s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.02158498764038086s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 9.655952453613281e-05s
Believability | Calculation of trust value for LODAC BDLS took 1.2874603271484375e-05s
INFO | --- Analysis for lodac-bdls took 142.9757170677185s
Availability | SPARQL endpoint availability check for lofd took 0.14339280128479004s
Availability | VoID file availability check for lofd took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for lofd took 0.3111119270324707s
Reputation | Calculation of the PageRank for lofd took 0.02120065689086914s
Interlinking | Calculation of Degree of Connection for lofd took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for lofd took 4.220008850097656e-05s
Believability | Calculation of trust value for lofd took 1.1444091796875e-05s
INFO | --- Analysis for lofd took 115.80140209197998s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 271.31926465034485s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0011763572692871094s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 28.35759401321411s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.021448850631713867s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 6.29425048828125e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 9.298324584960938e-06s
INFO | --- Analysis for loius took 730.9369220733643s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.2438507080078125e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.0008251667022705078s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.5560111999511719s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.02148747444152832s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 4.172325134277344e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 1.2874603271484375e-05s
INFO | --- Analysis for loius-linking-italian-university-statistics took 327.6623275279999s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.7154386043548584s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 24.558053016662598s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.022995471954345703s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.91278076171875e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 9.298324584960938e-06s
INFO | --- Analysis for london-gazette took 224.3356475830078s
Availability | SPARQL endpoint availability check for Weather Stations took 9.72747802734375e-05s
Availability | VoID file availability check for Weather Stations took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for Weather Stations took 26.459200382232666s
Reputation | Calculation of the PageRank for Weather Stations took 0.021822452545166016s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 9.894371032714844e-05s
Believability | Calculation of trust value for Weather Stations took 1.2636184692382812e-05s
INFO | --- Analysis for los_metar took 61.19479942321777s
Availability | SPARQL endpoint availability check for Lotico took 0.5430381298065186s
Availability | VoID file availability check for Lotico took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Lotico took 28.4123318195343s
Reputation | Calculation of the PageRank for Lotico took 0.022803544998168945s
Interlinking | Calculation of Degree of Connection for Lotico took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Lotico took 9.870529174804688e-05s
Believability | Calculation of trust value for Lotico took 1.7642974853515625e-05s
INFO | --- Analysis for lotico took 107.80190324783325s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.4749152660369873s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.000720977783203125s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 1.0646800994873047s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 1.1965155601501465s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.44406819343566895s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.7827427387237549s
Versatility | Languages check for Lower Layer Super Output Areas took 0.5374135971069336s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 30.215844869613647s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.2033827304840088s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.3453099727630615s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.1451256275177002s
Availability | RDF dump link check for Lower Layer Super Output Areas took 54.23196220397949s
License | MR license check for Lower Layer Super Output Areas took 0.36844968795776367s
License | HR license check for Lower Layer Super Output Areas took 30.244239807128906s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.23319625854492188s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.33501386642456055s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.3973381519317627s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.15096402168273926s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.20453381538391113s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.3315432071685791s
Performance | Throughput check for Lower Layer Super Output Areas took 12.58015513420105s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 8.392333984375e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.21805238723754883s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.29093503952026367s
Interlinking | skos check for Lower Layer Super Output Areas took 0.3159945011138916s
Interlinking | skos check for Lower Layer Super Output Areas took 0.4053051471710205s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.2630608081817627s
Currency | Creation date check for Lower Layer Super Output Areas took 0.484100341796875s
Currency | Modification date check for Lower Layer Super Output Areas took 0.35990166664123535s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 1.5254161357879639s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.2271709442138672s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.1464240550994873s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.20742464065551758s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.3543994426727295s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 0.8511960506439209s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 1.3345980644226074s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.670189380645752s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.0001647472381591797s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.43258047103881836s
Security | Sign check for Lower Layer Super Output Areas took 0.20281219482421875s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 29.144185066223145s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.022025346755981445s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 4.2438507080078125e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 9.5367431640625e-07s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.2874603271484375e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 464.4993727207184s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5040719509124756s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0005750656127929688s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 101.54842472076416s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9085609912872314s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.460809707641602s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.579729080200195s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2370779514313s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.147467851638794s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3768916130065918s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.38385820388794s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.36960673332214355s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9556291103363037s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.22255063056946s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2166609764099121s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.2746729850769043s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.2135794162750244s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5911929607391357s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2062852382659912s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.23915505409240723s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.073177099227905s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.677078247070312e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19921875s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19832158088684082s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.511751651763916s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.43880248069763184s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.922266244888306s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.46832966804504395s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.23276877403259277s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 148.0196509361267s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.18531060218811035s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5331661701202393s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.526552677154541s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 42.00856375694275s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.711289882659912s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.7412171363830566s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2156054973602295s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 86.31514430046082s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.4755539894104s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 31.11065983772278s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.5144078731536865s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 88.19825148582458s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.7484915256500244s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5611724853515625s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.2296085357666016s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.259855508804321s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 27.576438665390015s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.025973081588745117s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3113021850585938e-05s
INFO | --- Analysis for LPIS_(Poland) took 2347.8950617313385s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19724440574645996s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.00031256675720214844s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 103.17835450172424s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.927825927734375s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.13913345336914s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 14.127208471298218s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.17626905441284s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.9684584140777588s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21025323867797852s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.214675664901733s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.30028653144836426s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.7490606307983398s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.1999764442444s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2068483829498291s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.8861706256866455s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.9135456085205078s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4343891143798828s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.22196650505065918s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21966147422790527s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.130228281021118s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.00011205673217773438s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19921159744262695s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1899886131286621s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4382176399230957s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.42729687690734863s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.719585180282593s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4886767864227295s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.23081326484680176s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 159.48808813095093s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.239776611328125e-05s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2103571891784668s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3804912567138672s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.37555575370788574s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 40.13637161254883s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.6766369342803955s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.822934627532959s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19843769073486328s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 86.0154242515564s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.680588722229004s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 35.75435400009155s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.547011375427246s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 88.2079565525055s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.8816840648651123s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5667173862457275s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.2934823036193848s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 10.069705963134766s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 27.531506776809692s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.021560192108154297s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 6.890296936035156e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 2327.075696706772s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.482269287109375e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 21.944273233413696s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.02191615104675293s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.981590270996094e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 7.867813110351562e-06s
INFO | --- Analysis for lremap-auth took 144.24298858642578s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 9.34600830078125e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 20.072927236557007s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02266240119934082s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0008318424224853516s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 4.363059997558594e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.2636184692382812e-05s
INFO | --- Analysis for lremap-conf took 140.86638069152832s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.506111145019531e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0003440380096435547s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.27376508712768555s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.021495342254638672s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 4.124641418457031e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 8.58306884765625e-06s
INFO | --- Analysis for lremap-ri took 68.31905889511108s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 0.00015735626220703125s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.31128382682800293s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.02144789695739746s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.4809112548828125e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.33514404296875e-05s
INFO | --- Analysis for lremap-sub took 40.93704152107239s
Availability | SPARQL endpoint availability check for LSQ took 4.363059997558594e-05s
Availability | VoID file availability check for LSQ took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for LSQ took 19.055760145187378s
Reputation | Calculation of the PageRank for LSQ took 0.02109050750732422s
Interlinking | Calculation of Degree of Connection for LSQ took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.0994415283203125e-05s
Believability | Calculation of trust value for LSQ took 1.2636184692382812e-05s
INFO | --- Analysis for lsq took 122.94418811798096s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.6404926776885986s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 17.93665313720703s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.023892641067504883s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0010008811950683594s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 5.888938903808594e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 1.1444091796875e-05s
INFO | --- Analysis for LucaniPharsalia took 62.53161263465881s
Availability | SPARQL endpoint availability check for Linked rules took 9.202957153320312e-05s
Availability | VoID file availability check for Linked rules took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for Linked rules took 0.3329758644104004s
Reputation | Calculation of the PageRank for Linked rules took 0.022432565689086914s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.504753112792969e-05s
Believability | Calculation of trust value for Linked rules took 1.239776611328125e-05s
INFO | --- Analysis for Luminaires_senlis took 121.09863710403442s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 0.0001442432403564453s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.3233377933502197s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.02232980728149414s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0010466575622558594s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 3.933906555175781e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 1.2636184692382812e-05s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 124.80527138710022s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.24840021133423s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 18.09282946586609s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.022012710571289062s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 3.5762786865234375e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 8.106231689453125e-06s
INFO | --- Analysis for makg took 139.55180311203003s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 9.34600830078125e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.00041747093200683594s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.29691576957702637s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.0211336612701416s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 4.482269287109375e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 1.2159347534179688e-05s
INFO | --- Analysis for manchester-university-reading-lists took 60.07793855667114s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 9.298324584960938e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 23.43464422225952s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.021428823471069336s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0008194446563720703s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.5762786865234375e-05s
Believability | Calculation of trust value for engineering equipment ontology took 2.384185791015625e-05s
INFO | --- Analysis for manish took 185.62518548965454s
Availability | SPARQL endpoint availability check for MARC Codes List took 5.364418029785156e-05s
Availability | VoID file availability check for MARC Codes List took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for MARC Codes List took 22.13221764564514s
Reputation | Calculation of the PageRank for MARC Codes List took 0.028359651565551758s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0010523796081542969s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00017833709716796875s
Believability | Calculation of trust value for MARC Codes List took 1.1682510375976562e-05s
INFO | --- Analysis for marc-codes took 153.5661280155182s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.00010037422180175781s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 23.46367573738098s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.02222442626953125s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 5.3882598876953125e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.1682510375976562e-05s
INFO | --- Analysis for masc took 80.19312953948975s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.887580871582031e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.3096652030944824s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.023027420043945312s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 5.3882598876953125e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.4066696166992188e-05s
INFO | --- Analysis for masc-bn-nif took 112.60258316993713s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 0.16031479835510254s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.3406527042388916s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.02132558822631836s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 4.029273986816406e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 1.2636184692382812e-05s
INFO | --- Analysis for massobservationarchivecatalogue took 108.54817414283752s
Availability | SPARQL endpoint availability check for medline took 4.57763671875e-05s
Availability | VoID file availability check for medline took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for medline took 0.3010561466217041s
Reputation | Calculation of the PageRank for medline took 0.022345781326293945s
Interlinking | Calculation of Degree of Connection for medline took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for medline took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for medline took 3.886222839355469e-05s
Believability | Calculation of trust value for medline took 1.1920928955078125e-05s
INFO | --- Analysis for medline took 90.93008852005005s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.8451316356658936s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0007765293121337891s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 28.54595398902893s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.021299362182617188s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 7.963180541992188e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 1.2159347534179688e-05s
INFO | --- Analysis for meducator took 150.7738859653473s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 0.16109251976013184s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 22.186789751052856s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.0211184024810791s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 3.719329833984375e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 1.2159347534179688e-05s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 154.80561304092407s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.08229565620422363s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 29.637687921524048s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.021065950393676758s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 3.218650817871094e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.5735626220703125e-05s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 97.76929020881653s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 9.679794311523438e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.5164806842803955s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.021152019500732422s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 8.296966552734375e-05s
Believability | Calculation of trust value for MetaShare metadata model took 7.62939453125e-06s
INFO | --- Analysis for metashare took 106.52741837501526s
Availability | SPARQL endpoint availability check for MExiCo took 4.601478576660156e-05s
Availability | VoID file availability check for MExiCo took 0.0007719993591308594s
Completeness | Calculation of interlinking completeness for MExiCo took 26.712843656539917s
Reputation | Calculation of the PageRank for MExiCo took 0.021550655364990234s
Interlinking | Calculation of Degree of Connection for MExiCo took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for MExiCo took 5.626678466796875e-05s
Believability | Calculation of trust value for MExiCo took 1.4066696166992188e-05s
INFO | --- Analysis for mexico took 202.73388600349426s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.1241745948791504s
Availability | VoID file availability check for Coronavirus dataset took 0.0005373954772949219s
Extra | Recovery of all triples for Coronavirus dataset took 6.268612384796143s
Performance | Total latancy measurement for Coronavirus dataset took 2.6888339519500732s
Amount of data | Number of triples check for Coronavirus dataset took 1.2648179531097412s
Interoperability | New terms check for Coronavirus dataset took 2.7186954021453857s
Versatility | Languages check for Coronavirus dataset took 60.564751625061035s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.363136053085327s
Interpretability | RDF structures check for Coronavirus dataset took 0.5822651386260986s
Versatility | Serialization formats check for Coronavirus dataset took 0.587634801864624s
Availability | RDF dump link check for Coronavirus dataset took 0.5399003028869629s
License | MR license check for Coronavirus dataset took 0.6049900054931641s
License | HR license check for Coronavirus dataset took 41.4513680934906s
Amount of data | Number of property check for Coronavirus dataset took 0.5733804702758789s
Understandability | Number of label check for Coronavirus dataset took 0.9617230892181396s
Understandability | URI regex check for Coronavirus dataset took 1.0712573528289795s
Understandability | Vocabs check for Coronavirus dataset took 0.5404314994812012s
Verifiability | Authors check for Coronavirus dataset took 0.534475564956665s
Verifiability | Publishers check for Coronavirus dataset took 0.5387494564056396s
Performance | Throughput check for Coronavirus dataset took 10.608459234237671s
Amount of data | Check the number of entities for Coronavirus dataset took 8.845329284667969e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.5426506996154785s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5783872604370117s
Interlinking | skos check for Coronavirus dataset took 0.5989410877227783s
Interlinking | skos check for Coronavirus dataset took 0.5324609279632568s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.5512771606445312s
Currency | Creation date check for Coronavirus dataset took 1.1083669662475586s
Currency | Modification date check for Coronavirus dataset took 1.112745761871338s
Rep.Conc. | URIs length for Coronavirus dataset took 8.690080404281616s
Interoperability | New vocabularies check for Coronavirus dataset took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5677354335784912s
Accuracy | Check Functional Property for Coronavirus dataset took 0.8112425804138184s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.5792245864868164s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.373323917388916s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.022571325302124023s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.02964472770690918s
Consistency | Disjoint class check for Coronavirus dataset took 0.7092335224151611s
Consistency | Check Misplaced properties for Coronavirus dataset took 7.845291376113892s
Consistency | Misplaced classes for Coronavirus dataset took 0.6770203113555908s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.6334481239318848s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.3787286281585693s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.800273180007935s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.03330588340759277s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5832147598266602s
Security | Sign check for Coronavirus dataset took 0.5389065742492676s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3370.5637383461s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.29655933380126953s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021733999252319336s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 7.653236389160156e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 2.1457672119140625e-06s
Believability | Calculation of trust value for Coronavirus dataset took 8.344650268554688e-06s
INFO | --- Analysis for micro-coronavirus took 3729.7497584819794s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 4.744529724121094e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.20675158500671387s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.3146233558654785s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.020967483520507812s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00011897087097167969s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 8.821487426757812e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 162.2694022655487s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 5.507469177246094e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0003974437713623047s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.29738426208496094s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.021546363830566406s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00013113021850585938s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.2159347534179688e-05s
INFO | --- Analysis for mismuseos-gnoss took 82.04505729675293s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.10529470443725586s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 21.760431051254272s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.021569252014160156s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 5.602836608886719e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.2159347534179688e-05s
INFO | --- Analysis for mlsa took 165.64602398872375s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 9.012222290039062e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.3074319362640381s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.02216339111328125s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0011374950408935547s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 5.555152893066406e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 7.867813110351562e-06s
INFO | --- Analysis for model took 152.78726840019226s
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 6.532669067382812e-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.0007495880126953125s
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 24.944584131240845s
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.0216982364654541s
Interlinking | Calculation of Degree of Connection for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007817745208740234s
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 4.9591064453125e-05s
Believability | Calculation of trust value for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 1.239776611328125e-05s
INFO | --- Analysis for model1 took 158.36599016189575s
Availability | SPARQL endpoint availability check for Monumentos took 5.316734313964844e-05s
Availability | VoID file availability check for Monumentos took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for Monumentos took 0.3111147880554199s
Reputation | Calculation of the PageRank for Monumentos took 0.02166128158569336s
Interlinking | Calculation of Degree of Connection for Monumentos took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Monumentos took 4.1961669921875e-05s
Believability | Calculation of trust value for Monumentos took 8.344650268554688e-06s
INFO | --- Analysis for monumentos-zaragoza took 174.2015278339386s
Availability | SPARQL endpoint availability check for MORElab took 1.1214039325714111s
Availability | VoID file availability check for MORElab took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for MORElab took 23.134366512298584s
Reputation | Calculation of the PageRank for MORElab took 0.021183013916015625s
Interlinking | Calculation of Degree of Connection for MORElab took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for MORElab took 9.584426879882812e-05s
Believability | Calculation of trust value for MORElab took 1.1444091796875e-05s
INFO | --- Analysis for morelab took 92.85866737365723s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 1.9418079853057861s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0007503032684326172s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.32662534713745117s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.021244525909423828s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 9.34600830078125e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 1.1920928955078125e-05s
INFO | --- Analysis for msc took 75.12666893005371s
Availability | SPARQL endpoint availability check for Multext-East took 4.5299530029296875e-05s
Availability | VoID file availability check for Multext-East took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for Multext-East took 0.29432249069213867s
Reputation | Calculation of the PageRank for Multext-East took 0.02127981185913086s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.910064697265625e-05s
Believability | Calculation of trust value for Multext-East took 8.106231689453125e-06s
INFO | --- Analysis for multext-east took 23.698676586151123s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.649162292480469e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.3129770755767822s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.02123570442199707s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 4.291534423828125e-05s
Believability | Calculation of trust value for Multimedia Lab took 7.3909759521484375e-06s
INFO | --- Analysis for multimedia-lab took 71.83108639717102s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.8789710998535156s
Availability | VoID file availability check for Muninn World War I took 0.0007226467132568359s
Completeness | Calculation of interlinking completeness for Muninn World War I took 21.773473501205444s
Reputation | Calculation of the PageRank for Muninn World War I took 0.021544218063354492s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 9.34600830078125e-05s
Believability | Calculation of trust value for Muninn World War I took 7.62939453125e-06s
INFO | --- Analysis for muninn-world-war-i took 82.23564100265503s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0001270771026611328s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.3526268005371094s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.021809101104736328s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00011658668518066406s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.2159347534179688e-05s
INFO | --- Analysis for museosespania-gnoss took 210.72114849090576s
Availability | SPARQL endpoint availability check for Italian Museums took 1.4174909591674805s
Availability | VoID file availability check for Italian Museums took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for Italian Museums took 28.51397132873535s
Reputation | Calculation of the PageRank for Italian Museums took 0.021713972091674805s
Interlinking | Calculation of Degree of Connection for Italian Museums took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0008151531219482422s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 0.00010442733764648438s
Believability | Calculation of trust value for Italian Museums took 1.049041748046875e-05s
INFO | --- Analysis for museums-in-italy took 139.8937530517578s
Availability | SPARQL endpoint availability check for Muziekweb took 0.695573091506958s
Availability | VoID file availability check for Muziekweb took 0.0003447532653808594s
Extra | Recovery of all triples for Muziekweb took 1.4699828624725342s
Performance | Total latancy measurement for Muziekweb took 1.6058149337768555s
Amount of data | Number of triples check for Muziekweb took 0.3837249279022217s
Interoperability | New terms check for Muziekweb took 1.8180503845214844s
Versatility | Languages check for Muziekweb took 51.682995319366455s
Interpretability | Number of blank nodes check for Muziekweb took 0.318936824798584s
Interpretability | RDF structures check for Muziekweb took 0.6251258850097656s
Versatility | Serialization formats check for Muziekweb took 0.3379971981048584s
Availability | RDF dump link check for Muziekweb took 0.3206348419189453s
License | MR license check for Muziekweb took 0.35386109352111816s
License | HR license check for Muziekweb took 10.783401012420654s
Amount of data | Number of property check for Muziekweb took 0.30507898330688477s
Understandability | Number of label check for Muziekweb took 0.37160491943359375s
Understandability | URI regex check for Muziekweb took 0.6238243579864502s
Understandability | Vocabs check for Muziekweb took 0.328279972076416s
Verifiability | Authors check for Muziekweb took 0.3544940948486328s
Verifiability | Publishers check for Muziekweb took 0.2982668876647949s
Performance | Throughput check for Muziekweb took 12.37686824798584s
Amount of data | Check the number of entities for Muziekweb took 7.700920104980469e-05s
Verifiability | Contribs. check for Muziekweb took 0.3294534683227539s
Interlinking | sameAs chians check for Muziekweb took 0.33170485496520996s
Interlinking | skos check for Muziekweb took 0.40746498107910156s
Interlinking | skos check for Muziekweb took 0.3086709976196289s
Timeliness | dataset update frequency check for Muziekweb took 0.31384992599487305s
Currency | Creation date check for Muziekweb took 0.8044955730438232s
Currency | Modification date check for Muziekweb took 0.847783088684082s
Rep.Conc. | URIs length for Muziekweb took 1.9885609149932861s
Interoperability | New vocabularies check for Muziekweb took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.29784107208251953s
Accuracy | Check Functional Property for Muziekweb took 0.5049562454223633s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.5412585735321045s
Accuracy | Check Empty annotation labels for Muziekweb took 0.8472700119018555s
Accuracy | Check White space in annotation for Muziekweb took 0.028085708618164062s
Accuracy | Check Datatype consistency for Muziekweb took 0.029735803604125977s
Consistency | Disjoint class check for Muziekweb took 0.47959256172180176s
Consistency | Check Misplaced properties for Muziekweb took 1.126049280166626s
Consistency | Check Ontology hijacking for Muziekweb took 2.1377055644989014s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.363966703414917s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.666146993637085s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03402590751647949s
Conciseness | Check Intensional conciseness for Muziekweb took 0.2920558452606201s
Security | Sign check for Muziekweb took 0.38068532943725586s
Availability | Check URIs Dereferenciability for Muziekweb took 1986.5566816329956s
Completeness | Calculation of interlinking completeness for Muziekweb took 21.42440390586853s
Reputation | Calculation of the PageRank for Muziekweb took 0.021506547927856445s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 8.0108642578125e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.9073486328125e-06s
Believability | Calculation of trust value for Muziekweb took 1.2874603271484375e-05s
INFO | --- Analysis for muziekweb took 2200.016755104065s
Availability | SPARQL endpoint availability check for myExperiment took 0.5476808547973633s
Availability | VoID file availability check for myExperiment took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for myExperiment took 20.321122884750366s
Reputation | Calculation of the PageRank for myExperiment took 0.02140069007873535s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.0001125335693359375s
Believability | Calculation of trust value for myExperiment took 1.3589859008789062e-05s
INFO | --- Analysis for my-experiment took 158.35636448860168s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.08100056648254395s
Availability | VoID file availability check for My Family Lineage took 0.0004057884216308594s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.41870999336242676s
Reputation | Calculation of the PageRank for My Family Lineage took 0.02139115333557129s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 9.441375732421875e-05s
Believability | Calculation of trust value for My Family Lineage took 8.344650268554688e-06s
INFO | --- Analysis for my-family-lineage took 101.20442938804626s
Availability | SPARQL endpoint availability check for My ontology test took 10.48604965209961s
Availability | VoID file availability check for My ontology test took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for My ontology test took 0.27872776985168457s
Reputation | Calculation of the PageRank for My ontology test took 0.02150130271911621s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0009987354278564453s
Interlinking | Calculation of Clustering coefficient for My ontology test took 4.9114227294921875e-05s
Believability | Calculation of trust value for My ontology test took 1.1920928955078125e-05s
INFO | --- Analysis for myontologytest took 139.89697813987732s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 9.34600830078125e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0013959407806396484s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 26.48859167098999s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.021401405334472656s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.00012612342834472656s
Believability | Calculation of trust value for myopenlink dataspaces took 1.239776611328125e-05s
INFO | --- Analysis for myopenlink-dataspaces took 128.87895393371582s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 8.24777865409851s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.3332991600036621s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.021475791931152344s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 8.273124694824219e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for n-lex-as-linked-data took 196.49373984336853s
Availability | SPARQL endpoint availability check for NAICS 2007 took 25.904804229736328s
Availability | VoID file availability check for NAICS 2007 took 0.0010030269622802734s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 27.249359607696533s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.021439313888549805s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.744529724121094e-05s
Believability | Calculation of trust value for NAICS 2007 took 9.5367431640625e-06s
INFO | --- Analysis for naics-2007 took 282.2278583049774s
Availability | SPARQL endpoint availability check for NAICS 2012 took 25.110580921173096s
Availability | VoID file availability check for NAICS 2012 took 0.0009484291076660156s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 30.08414387702942s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.022670507431030273s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.9604644775390625e-05s
Believability | Calculation of trust value for NAICS 2012 took 9.775161743164062e-06s
INFO | --- Analysis for naics-2012 took 327.8350737094879s
Availability | SPARQL endpoint availability check for Usernames  took 9.822845458984375e-05s
Availability | VoID file availability check for Usernames  took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Usernames  took 29.695210456848145s
Reputation | Calculation of the PageRank for Usernames  took 0.0294339656829834s
Interlinking | Calculation of Degree of Connection for Usernames  took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.933906555175781e-05s
Believability | Calculation of trust value for Usernames  took 7.867813110351562e-06s
INFO | --- Analysis for Names took 207.01127791404724s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.1873054504394531s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0007112026214599609s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.442077875137329s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 3.0071496963500977s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 11.503610849380493s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 15.583070516586304s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.39345431327819824s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.928214311599731s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.3498823642730713s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.34484267234802246s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.3510439395904541s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.3782389163970947s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.8343982696533203s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.81322813034058s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.8566892147064209s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 6.838612079620361s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.720341682434082s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.8417305946350098s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.3680906295776367s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.8136968612670898s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 12.978573560714722s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 8.726119995117188e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.8203012943267822s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.4874882698059082s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.9114766120910645s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.0444812774658203s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.36180686950683594s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.1037440299987793s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.690018892288208s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.2231769561767578s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.3433804512023926s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3792726993560791s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.38135528564453125s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.38254809379577637s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0003261566162109375s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0005106925964355469s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.8125708103179932s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.7538015842437744s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.3434932231903076s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.77358078956604s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.3868038654327393s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.7847318649291992s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0007119178771972656s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.8443937301635742s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 4.51572060585022s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.31880688667297363s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.022100210189819336s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 7.009506225585938e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.430511474609375e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 9.059906005859375e-06s
INFO | --- Analysis for national-diet-library-authorities took 358.92841720581055s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.8224139213562012s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0006644725799560547s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.4316060543060303s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 3.112128496170044s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.401976346969604s
Interoperability | New terms check for National Diet Library of Japan subject headings took 19.560882091522217s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.8388652801513672s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.953587293624878s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.33086347579956055s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.3782048225402832s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.8361139297485352s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.36980605125427246s
License | MR license check for National Diet Library of Japan subject headings took 0.3817751407623291s
License | HR license check for National Diet Library of Japan subject headings took 91.78579044342041s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8804891109466553s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.1360602378845215s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.7205572128295898s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.3492302894592285s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.34024810791015625s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.3710770606994629s
Performance | Throughput check for National Diet Library of Japan subject headings took 12.444420576095581s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 9.036064147949219e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.8269686698913574s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.9122219085693359s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.3381659984588623s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.0451900959014893s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.3644294738769531s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.585111379623413s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.6874034404754639s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.7100229263305664s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.3551170825958252s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.3685033321380615s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.783951997756958s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.3499569892883301s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007457733154296875s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.001056671142578125s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.353895902633667s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.6684021949768066s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.3591427803039551s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.7800302505493164s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.3862321376800537s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.7101616859436035s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0006721019744873047s
Security | Sign check for National Diet Library of Japan subject headings took 0.3720228672027588s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 4.809229373931885s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.29423046112060547s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02210378646850586s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 2.288818359375e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0010385513305664062s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 7.581710815429688e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 1.2636184692382812e-05s
INFO | --- Analysis for national-diet-library-subject-headings took 315.86871457099915s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.1089198589324951s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.00041747093200683594s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 25.580196857452393s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.022077560424804688s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 5.5789947509765625e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 1.239776611328125e-05s
INFO | --- Analysis for national-library-of-greece-authority-records took 113.59979581832886s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 5.507469177246094e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007519721984863281s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 23.780144691467285s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.021402835845947266s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.796287536621094e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.1682510375976562e-05s
INFO | --- Analysis for Naturopathy took 114.13859176635742s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 0.19292593002319336s
Availability | VoID file availability check for NCI Thesaurus took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.5205378532409668s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.021294593811035156s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.933906555175781e-05s
Believability | Calculation of trust value for NCI Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for nci-thesaurus took 176.07921266555786s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.7091007232666016s
Availability | VoID file availability check for COVID-19 Data took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 26.510117769241333s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.022269725799560547s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0008082389831542969s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 4.100799560546875e-05s
Believability | Calculation of trust value for COVID-19 Data took 7.867813110351562e-06s
INFO | --- Analysis for NCMI-COVID-19 took 194.63618683815002s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.5879452228546143s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.2906794548034668s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.021369218826293945s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.8835067749023438e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 1.3113021850585938e-05s
INFO | --- Analysis for NCMICOVID-19 took 181.00158429145813s
Availability | SPARQL endpoint availability check for NDF-RT took 0.09445047378540039s
Availability | VoID file availability check for NDF-RT took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for NDF-RT took 24.18246340751648s
Reputation | Calculation of the PageRank for NDF-RT took 0.026843786239624023s
Interlinking | Calculation of Degree of Connection for NDF-RT took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.001748800277709961s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 6.389617919921875e-05s
Believability | Calculation of trust value for NDF-RT took 9.298324584960938e-06s
INFO | --- Analysis for ndf-rt took 177.17502975463867s
Availability | SPARQL endpoint availability check for Near took 0.0001049041748046875s
Availability | VoID file availability check for Near took 0.0005967617034912109s
Completeness | Calculation of interlinking completeness for Near took 24.853412628173828s
Reputation | Calculation of the PageRank for Near took 0.0211794376373291s
Interlinking | Calculation of Degree of Connection for Near took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Near took 0.0008351802825927734s
Interlinking | Calculation of Clustering coefficient for Near took 9.799003601074219e-05s
Believability | Calculation of trust value for Near took 1.1920928955078125e-05s
INFO | --- Analysis for near took 154.7691090106964s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 9.012222290039062e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.5478465557098389s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.022687911987304688s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.814697265625e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.239776611328125e-05s
INFO | --- Analysis for neurolex-wiki took 179.50536274909973s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 8.988380432128906e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0007712841033935547s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 25.262504816055298s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.021402835845947266s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 5.173683166503906e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 1.2159347534179688e-05s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 54.34096884727478s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.601478576660156e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 25.87190294265747s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.02149176597595215s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.000835418701171875s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 9.441375732421875e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 8.106231689453125e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 129.70575046539307s
Availability | SPARQL endpoint availability check for neXtProt took 1.7177329063415527s
Availability | VoID file availability check for neXtProt took 0.0003314018249511719s
Completeness | Calculation of interlinking completeness for neXtProt took 0.43804144859313965s
Reputation | Calculation of the PageRank for neXtProt took 0.021800756454467773s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0008757114410400391s
Interlinking | Calculation of Clustering coefficient for neXtProt took 4.696846008300781e-05s
Believability | Calculation of trust value for neXtProt took 1.5497207641601562e-05s
INFO | --- Analysis for nextprot took 130.3371503353119s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.506111145019531e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 23.894657850265503s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.021284103393554688s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0008196830749511719s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00012302398681640625s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.3113021850585938e-05s
INFO | --- Analysis for nextweb-gnoss took 140.736474275589s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.9591064453125e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 25.145703554153442s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.021245241165161133s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.225440979003906e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 9.298324584960938e-06s
INFO | --- Analysis for nhs-jargon took 169.67333984375s
Availability | SPARQL endpoint availability check for NIT Patna took 9.846687316894531e-05s
Availability | VoID file availability check for NIT Patna took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for NIT Patna took 26.579052448272705s
Reputation | Calculation of the PageRank for NIT Patna took 0.02176499366760254s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 8.869171142578125e-05s
Believability | Calculation of trust value for NIT Patna took 1.1920928955078125e-05s
INFO | --- Analysis for NITP took 203.07111144065857s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.458427429199219e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.2889893054962158s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.021419286727905273s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0008592605590820312s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.886222839355469e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 1.3113021850585938e-05s
INFO | --- Analysis for nlr-dataset-mod took 161.22090029716492s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.5850241184234619s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 23.400797843933105s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.021743297576904297s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 5.507469177246094e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for NLW took 127.42903804779053s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.718851089477539s
Availability | VoID file availability check for Nobel Prizes took 0.3574039936065674s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 28.287238836288452s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.023041486740112305s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 0.00010132789611816406s
Believability | Calculation of trust value for Nobel Prizes took 1.1682510375976562e-05s
INFO | --- Analysis for nobelprizes took 64.78230905532837s
Availability | SPARQL endpoint availability check for NoiPA took 0.31165337562561035s
Availability | VoID file availability check for NoiPA took 0.0006051063537597656s
Extra | Recovery of all triples for NoiPA took 1.5065996646881104s
Performance | Total latancy measurement for NoiPA took 1.0639119148254395s
Amount of data | Number of triples check for NoiPA took 3.4971272945404053s
Interoperability | New terms check for NoiPA took 2.9191956520080566s
Versatility | Languages check for NoiPA took 60.214826822280884s
Interpretability | Number of blank nodes check for NoiPA took 0.22269439697265625s
Interpretability | RDF structures check for NoiPA took 0.30098628997802734s
Versatility | Serialization formats check for NoiPA took 0.2322702407836914s
Availability | RDF dump link check for NoiPA took 0.28089189529418945s
License | MR license check for NoiPA took 0.3709580898284912s
License | HR license check for NoiPA took 60.24288845062256s
Amount of data | Number of property check for NoiPA took 0.2937448024749756s
Understandability | Number of label check for NoiPA took 0.5031993389129639s
Understandability | URI regex check for NoiPA took 0.3586866855621338s
Understandability | Vocabs check for NoiPA took 0.1948401927947998s
Verifiability | Authors check for NoiPA took 0.12178587913513184s
Verifiability | Publishers check for NoiPA took 0.2151796817779541s
Performance | Throughput check for NoiPA took 10.727696180343628s
Amount of data | Check the number of entities for NoiPA took 6.270408630371094e-05s
Verifiability | Contribs. check for NoiPA took 0.14042186737060547s
Interlinking | sameAs chians check for NoiPA took 0.12111544609069824s
Interlinking | skos check for NoiPA took 0.4732372760772705s
Interlinking | skos check for NoiPA took 0.12389588356018066s
Timeliness | dataset update frequency check for NoiPA took 0.1515672206878662s
Currency | Creation date check for NoiPA took 0.2586369514465332s
Currency | Modification date check for NoiPA took 0.12493300437927246s
Rep.Conc. | URIs length for NoiPA took 18.03586983680725s
Interoperability | New vocabularies check for NoiPA took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.2775120735168457s
Accuracy | Check Functional Property for NoiPA took 0.20144891738891602s
Accuracy | Check Inverse Functional Property for NoiPA took 0.17219829559326172s
Accuracy | Check Empty annotation labels for NoiPA took 0.3823273181915283s
Accuracy | Check White space in annotation for NoiPA took 0.02632451057434082s
Accuracy | Check Datatype consistency for NoiPA took 0.030009746551513672s
Consistency | Disjoint class check for NoiPA took 0.20113301277160645s
Consistency | Check Misplaced properties for NoiPA took 16.407877683639526s
Consistency | Misplaced classes for NoiPA took 0.3220028877258301s
Consistency | Check Ontology hijacking for NoiPA took 1.7797765731811523s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.357119083404541s
Consistency | Check Invalid usage of undefined properties for NoiPA took 17.46977138519287s
Conciseness | Check Extensional conciseness for NoiPA took 0.035658836364746094s
Conciseness | Check Intensional conciseness for NoiPA took 0.22589445114135742s
Security | Sign check for NoiPA took 0.1757674217224121s
Availability | Check URIs Dereferenciability for NoiPA took 11.28797698020935s
Completeness | Calculation of interlinking completeness for NoiPA took 25.749701976776123s
Reputation | Calculation of the PageRank for NoiPA took 0.021817922592163086s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for NoiPA took 4.3392181396484375e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.6689300537109375e-06s
Believability | Calculation of trust value for NoiPA took 1.1920928955078125e-05s
INFO | --- Analysis for NoiPA took 672.3274102210999s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 0.9004490375518799s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0007860660552978516s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 25.280163049697876s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.021775484085083008s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 0.0001087188720703125s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.4543533325195312e-05s
INFO | --- Analysis for nom took 141.2030749320984s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 25.523248434066772s
Availability | VoID file availability check for Nomenclator Asturias took 0.000865936279296875s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.3320014476776123s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.021532535552978516s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 9.441375732421875e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 9.775161743164062e-06s
INFO | --- Analysis for nomenclator-asturias took 339.8012766838074s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.37445521354675293s
Availability | VoID file availability check for Nomisma.org  took 0.0004489421844482422s
Extra | Recovery of all triples for Nomisma.org  took 627.404230594635s
Performance | Total latancy measurement for Nomisma.org  took 1.5363154411315918s
Amount of data | Number of triples check for Nomisma.org  took 30.115134239196777s
Interoperability | New terms check for Nomisma.org  took 5.270328998565674s
Versatility | Languages check for Nomisma.org  took 94.01714491844177s
Interpretability | Number of blank nodes check for Nomisma.org  took 28.081274271011353s
Security | Check HTTPS for Nomisma.org  took 0.7027587890625s
Interpretability | RDF structures check for Nomisma.org  took 0.35462307929992676s
Versatility | Serialization formats check for Nomisma.org  took 0.33876729011535645s
Availability | RDF dump link check for Nomisma.org  took 989.1067342758179s
License | MR license check for Nomisma.org  took 0.36007237434387207s
License | HR license check for Nomisma.org  took 57.927940368652344s
Amount of data | Number of property check for Nomisma.org  took 0.3649744987487793s
Understandability | Number of label check for Nomisma.org  took 8.476634979248047s
Understandability | URI regex check for Nomisma.org  took 0.6247761249542236s
Understandability | Vocabs check for Nomisma.org  took 0.29862189292907715s
Verifiability | Authors check for Nomisma.org  took 0.2945988178253174s
Verifiability | Publishers check for Nomisma.org  took 0.3354330062866211s
Performance | Throughput check for Nomisma.org  took 11.668676137924194s
Amount of data | Check the number of entities for Nomisma.org  took 64.61276030540466s
Verifiability | Contribs. check for Nomisma.org  took 0.37762022018432617s
Interlinking | sameAs chians check for Nomisma.org  took 0.3239326477050781s
Interlinking | skos check for Nomisma.org  took 0.9724607467651367s
Interlinking | skos check for Nomisma.org  took 0.45742225646972656s
Timeliness | dataset update frequency check for Nomisma.org  took 0.3067023754119873s
Currency | Creation date check for Nomisma.org  took 0.6607840061187744s
Currency | Modification date check for Nomisma.org  took 0.653989315032959s
Rep.Conc. | URIs length for Nomisma.org  took 273.39453887939453s
Interoperability | New vocabularies check for Nomisma.org  took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.34007883071899414s
Accuracy | Check Functional Property for Nomisma.org  took 0.34298133850097656s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.29163575172424316s
Accuracy | Check Empty annotation labels for Nomisma.org  took 192.90452361106873s
Accuracy | Check White space in annotation for Nomisma.org  took 2.766578197479248s
Accuracy | Check Datatype consistency for Nomisma.org  took 5.621286869049072s
Consistency | Disjoint class check for Nomisma.org  took 0.34697985649108887s
Consistency | Check Misplaced properties for Nomisma.org  took 24.76163673400879s
Consistency | Check Ontology hijacking for Nomisma.org  took 186.49851250648499s
Consistency | Check Invalid usage of undefined classes for Nomisma.org  took 2.2449593544006348s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 26.43573760986328s
Conciseness | Check Extensional conciseness for Nomisma.org  took 2.8341856002807617s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.3446013927459717s
Security | Sign check for Nomisma.org  took 0.3352324962615967s
Availability | Check URIs Dereferenciability for Nomisma.org  took 1654.3289840221405s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 29.327754020690918s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.026279687881469727s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 7.772445678710938e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 2.384185791015625e-06s
Believability | Calculation of trust value for Nomisma.org  took 1.1444091796875e-05s
INFO | --- Analysis for nomisma_org took 7208.468477010727s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.37262487411499023s
Availability | VoID file availability check for Curriculum Vitae took 0.0005733966827392578s
Extra | Recovery of all triples for Curriculum Vitae took 0.6463263034820557s
Performance | Total latancy measurement for Curriculum Vitae took 1.2645130157470703s
Amount of data | Number of triples check for Curriculum Vitae took 0.13837194442749023s
Interoperability | New terms check for Curriculum Vitae took 1.794145107269287s
Versatility | Languages check for Curriculum Vitae took 0.21638202667236328s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.2584397792816162s
Interpretability | RDF structures check for Curriculum Vitae took 0.1659221649169922s
Versatility | Serialization formats check for Curriculum Vitae took 0.1370410919189453s
Availability | RDF dump link check for Curriculum Vitae took 0.27097606658935547s
License | MR license check for Curriculum Vitae took 0.1499631404876709s
License | HR license check for Curriculum Vitae took 0.16941475868225098s
Amount of data | Number of property check for Curriculum Vitae took 0.25678324699401855s
Understandability | Number of label check for Curriculum Vitae took 0.19056463241577148s
Understandability | URI regex check for Curriculum Vitae took 0.3687708377838135s
Understandability | Vocabs check for Curriculum Vitae took 0.22912883758544922s
Verifiability | Authors check for Curriculum Vitae took 0.13659191131591797s
Verifiability | Publishers check for Curriculum Vitae took 0.2530388832092285s
Performance | Throughput check for Curriculum Vitae took 10.65243935585022s
Amount of data | Check the number of entities for Curriculum Vitae took 7.343292236328125e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.1250765323638916s
Interlinking | sameAs chians check for Curriculum Vitae took 0.12811994552612305s
Interlinking | skos check for Curriculum Vitae took 0.14543437957763672s
Interlinking | skos check for Curriculum Vitae took 0.1413118839263916s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.12579059600830078s
Currency | Creation date check for Curriculum Vitae took 0.3456287384033203s
Currency | Modification date check for Curriculum Vitae took 0.3297102451324463s
Rep.Conc. | URIs length for Curriculum Vitae took 0.37793540954589844s
Interoperability | New vocabularies check for Curriculum Vitae took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.12391996383666992s
Accuracy | Check Functional Property for Curriculum Vitae took 0.14670252799987793s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.13729548454284668s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.1504957675933838s
Accuracy | Check White space in annotation for Curriculum Vitae took 0.00010275840759277344s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.004511356353759766s
Consistency | Disjoint class check for Curriculum Vitae took 0.13440346717834473s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.25446367263793945s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.8005499839782715s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.7175993919372559s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.8812708854675293s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0014302730560302734s
Security | Sign check for Curriculum Vitae took 0.14959311485290527s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 19.78985023498535s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.33797621726989746s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.022217273712158203s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.1920928955078125e-06s
Believability | Calculation of trust value for Curriculum Vitae took 1.5974044799804688e-05s
INFO | --- Analysis for Nordine_Bittich took 161.96913814544678s
Availability | SPARQL endpoint availability check for NorPark took 0.2392258644104004s
Availability | VoID file availability check for NorPark took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for NorPark took 0.30769872665405273s
Reputation | Calculation of the PageRank for NorPark took 0.02156376838684082s
Interlinking | Calculation of Degree of Connection for NorPark took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0008559226989746094s
Interlinking | Calculation of Clustering coefficient for NorPark took 7.319450378417969e-05s
Believability | Calculation of trust value for NorPark took 1.2159347534179688e-05s
INFO | --- Analysis for norpark took 118.63073301315308s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.026117324829101562s
Availability | VoID file availability check for Parking Dataset took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Parking Dataset took 28.578493118286133s
Reputation | Calculation of the PageRank for Parking Dataset took 0.022695064544677734s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 5.91278076171875e-05s
Believability | Calculation of trust value for Parking Dataset took 1.2874603271484375e-05s
INFO | --- Analysis for norpark2 took 213.2013440132141s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.5974326133728027s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0005128383636474609s
Extra | Recovery of all triples for Norway fishery stocks dataset took 115.90968155860901s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.992699146270752s
Amount of data | Number of triples check for Norway fishery stocks dataset took 9.27291989326477s
Interoperability | New terms check for Norway fishery stocks dataset took 14.408737421035767s
Versatility | Languages check for Norway fishery stocks dataset took 300.2194685935974s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 2.22611927986145s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.3161351680755615s
Versatility | Serialization formats check for Norway fishery stocks dataset took 6.4629716873168945s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.31572580337524414s
License | MR license check for Norway fishery stocks dataset took 0.7476749420166016s
License | HR license check for Norway fishery stocks dataset took 300.19848370552063s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.2324526309967041s
Understandability | Number of label check for Norway fishery stocks dataset took 2.6592037677764893s
Understandability | URI regex check for Norway fishery stocks dataset took 1.0590436458587646s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.5308794975280762s
Verifiability | Authors check for Norway fishery stocks dataset took 0.19637393951416016s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.2623555660247803s
Performance | Throughput check for Norway fishery stocks dataset took 11.433839559555054s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 0.00011038780212402344s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.20166730880737305s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.2045154571533203s
Interlinking | skos check for Norway fishery stocks dataset took 0.5464005470275879s
Interlinking | skos check for Norway fishery stocks dataset took 0.4194459915161133s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 5.135791063308716s
Currency | Creation date check for Norway fishery stocks dataset took 0.4909224510192871s
Currency | Modification date check for Norway fishery stocks dataset took 0.2530360221862793s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 151.17592239379883s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.2126929759979248s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.45353102684020996s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.45882081985473633s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 34.51467561721802s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.6789844036102295s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.7087604999542236s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.18366217613220215s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 86.99315071105957s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.403071403503418s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 40.893229246139526s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.5138723850250244s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 87.30513048171997s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.7986648082733154s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.6298947334289551s
Security | Sign check for Norway fishery stocks dataset took 1.5541284084320068s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 9.971661806106567s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 30.515113830566406s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.023451566696166992s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 9.775161743164062e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 1.2636184692382812e-05s
INFO | --- Analysis for Norway_Fishery_ took 2432.536539077759s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.49909520149230957s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 29.75653576850891s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.021131038665771484s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 5.269050598144531e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.2159347534179688e-05s
INFO | --- Analysis for norwegian-geo-divisions took 108.72137117385864s
Availability | SPARQL endpoint availability check for NITP took 8.7738037109375e-05s
Availability | VoID file availability check for NITP took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for NITP took 0.3130514621734619s
Reputation | Calculation of the PageRank for NITP took 0.021028757095336914s
Interlinking | Calculation of Degree of Connection for NITP took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for NITP took 7.891654968261719e-05s
Believability | Calculation of trust value for NITP took 1.2159347534179688e-05s
INFO | --- Analysis for notIdentifier took 165.1151237487793s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 0.00010251998901367188s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.3295586109161377s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.021457672119140625s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0011038780212402344s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 5.5789947509765625e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 1.3113021850585938e-05s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 105.18718600273132s
Availability | SPARQL endpoint availability check for NPM took 7.772445678710938e-05s
Availability | VoID file availability check for NPM took 0.0007023811340332031s
Completeness | Calculation of interlinking completeness for NPM took 0.3282434940338135s
Reputation | Calculation of the PageRank for NPM took 0.021260499954223633s
Interlinking | Calculation of Degree of Connection for NPM took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for NPM took 4.100799560546875e-05s
Believability | Calculation of trust value for NPM took 1.239776611328125e-05s
INFO | --- Analysis for npm took 52.70003843307495s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.0504915714263916s
Availability | VoID file availability check for NTNU special collections took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for NTNU special collections took 25.637495756149292s
Reputation | Calculation of the PageRank for NTNU special collections took 0.021399974822998047s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0008180141448974609s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 6.771087646484375e-05s
Believability | Calculation of trust value for NTNU special collections took 1.1920928955078125e-05s
INFO | --- Analysis for ntnusc took 132.37697291374207s
Availability | SPARQL endpoint availability check for links took 5.698204040527344e-05s
Availability | VoID file availability check for links took 0.00054931640625s
Completeness | Calculation of interlinking completeness for links took 0.2935929298400879s
Reputation | Calculation of the PageRank for links took 0.021120309829711914s
Interlinking | Calculation of Degree of Connection for links took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for links took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for links took 1.4066696166992188e-05s
Believability | Calculation of trust value for links took 7.62939453125e-06s
INFO | --- Analysis for nugmyanmar took 109.70458960533142s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 0.00010514259338378906s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 22.094520568847656s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.02109241485595703s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 0.00011134147644042969s
Believability | Calculation of trust value for NUTS (GeoVocab) took 9.775161743164062e-06s
INFO | --- Analysis for nuts-geovocab took 106.0585503578186s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.48034191131591797s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 25.164694786071777s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.021273374557495117s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 7.796287536621094e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 1.2159347534179688e-05s
INFO | --- Analysis for nvd took 200.18299794197083s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.7349269390106201s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.45479798316955566s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.3213217258453369s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.0211794376373291s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.535385131835938e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.239776611328125e-05s
INFO | --- Analysis for nvs took 181.475919008255s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 9.131431579589844e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 27.13079047203064s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.02137446403503418s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0008246898651123047s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00021219253540039062s
Believability | Calculation of trust value for New York Times - Linked Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for nytimes-linked-open-data took 154.4115390777588s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 8.821487426757812e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.3707876205444336s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.021226882934570312s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 3.838539123535156e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 7.867813110351562e-06s
INFO | --- Analysis for o-anc took 125.06011128425598s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 6.127357482910156e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.0003039836883544922s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.30509138107299805s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.0211029052734375s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 8.630752563476562e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 7.867813110351562e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 154.69094705581665s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.5593361854553223s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0007219314575195312s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.529463291168213s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.864029884338379s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 3.2833316326141357s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.827857494354248s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 58.33865571022034s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.538170099258423s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.2745683193206787s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.337268590927124s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.4933342933654785s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.5023684501647949s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.3886079788208008s
License | HR license check for Italian Chamber of Deputies - official dataset took 58.27731728553772s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.4910576343536377s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.61663818359375s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.7821521759033203s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.4876108169555664s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.30298733711242676s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.3816075325012207s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 12.123297214508057s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 7.62939453125e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.3684706687927246s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.3837878704071045s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.3685007095336914s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.39551639556884766s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.5024778842926025s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.6688632965087891s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.3570082187652588s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 16.791441202163696s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.35353565216064453s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.38735437393188477s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.3808608055114746s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.7628574371337891s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.023772239685058594s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.029432058334350586s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.3974111080169678s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 12.725588321685791s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.46997690200805664s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.1151342391967773s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.3698501586914062s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 13.624981164932251s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03355264663696289s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.43015265464782715s
Security | Sign check for Italian Chamber of Deputies - official dataset took 1.3748338222503662s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 9.369700193405151s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.3586282730102539s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.021177291870117188s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00010013580322265625s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 1.7642974853515625e-05s
INFO | --- Analysis for ocd took 490.87278389930725s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 5.0067901611328125e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 29.019110202789307s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 4.76837158203125e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.2159347534179688e-05s
INFO | --- Analysis for oceandrilling-borehole took 141.60133695602417s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 3.3346455097198486s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.6114752292633057s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 23.99329900741577s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.021223783493041992s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0009407997131347656s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 0.00012063980102539062s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.33514404296875e-05s
INFO | --- Analysis for oceandrilling-codices took 164.95433712005615s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 3.577423334121704s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.2930452823638916s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.02152252197265625s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 4.1484832763671875e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.3113021850585938e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 61.6227912902832s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 3.4885098934173584s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0007703304290771484s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 25.99898672103882s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.02098560333251953s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 5.7220458984375e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.1682510375976562e-05s
INFO | --- Analysis for oceandrilling-forams took 158.89247822761536s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 3.450291395187378s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 25.5586359500885s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.02109360694885254s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 4.076957702636719e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 8.58306884765625e-06s
INFO | --- Analysis for oceandrilling-janus took 131.89901041984558s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 12.910489320755005s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0007917881011962891s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.3033022880554199s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.021416664123535156s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 5.1975250244140625e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.1920928955078125e-05s
INFO | --- Analysis for oceandrilling-janusamp took 201.29688572883606s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.0262200832366943s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 25.898917198181152s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.021582841873168945s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 4.1961669921875e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.2636184692382812e-05s
INFO | --- Analysis for oceandrilling-ldeo took 138.48172855377197s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.410743713378906e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0007483959197998047s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.3160684108734131s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.021950483322143555s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0009720325469970703s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 7.319450378417969e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.2636184692382812e-05s
INFO | --- Analysis for oclc-fast took 34.852585315704346s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 6.413459777832031e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007672309875488281s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.35684800148010254s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.021051883697509766s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0008509159088134766s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.9577484130859375e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 9.775161743164062e-06s
INFO | --- Analysis for odc-imd-environment-score took 109.52273368835449s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.5033903121948242s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0006220340728759766s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 1.221095085144043s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 0.9335286617279053s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.4123687744140625s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.8478202819824219s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.4882690906524658s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 30.186784982681274s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.10549807548522949s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.38822197914123535s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.21157360076904297s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 49.28532886505127s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.2713663578033447s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 30.180184841156006s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.2040095329284668s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.2455739974975586s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.501739501953125s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.20653700828552246s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.13243889808654785s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.32851362228393555s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 12.086954355239868s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 7.271766662597656e-05s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.14847660064697266s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.28241658210754395s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.30077624320983887s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.20405364036560059s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.21679210662841797s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.8710906505584717s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.23551630973815918s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 2.133121967315674s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.14760804176330566s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.22077107429504395s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.34835076332092285s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.3635377883911133s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.766638994216919s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 1.2357254028320312s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.6065056324005127s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.00018715858459472656s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.46550655364990234s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.1423020362854004s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 25.575629949569702s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.021463871002197266s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 5.173683166503906e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 1.1920928955078125e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 1.0251998901367188e-05s
INFO | --- Analysis for odc-lsoa took 419.37718772888184s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 0.9599130153656006s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.3030531406402588s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.021268129348754883s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 4.0531158447265625e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 1.2874603271484375e-05s
INFO | --- Analysis for ods took 130.7811405658722s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.10868430137634277s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 27.224046230316162s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.021012067794799805s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.00010371208190917969s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for oecd-linked-data took 79.88630890846252s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.130089282989502s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0008206367492675781s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.3067493438720703s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.02138495445251465s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.935264587402344e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 1.239776611328125e-05s
INFO | --- Analysis for ogolod took 205.26237630844116s
Availability | SPARQL endpoint availability check for OLAC Metadata took 4.76837158203125e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0008206367492675781s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.3685302734375s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.021147489547729492s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0008904933929443359s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 6.175041198730469e-05s
Believability | Calculation of trust value for OLAC Metadata took 1.1682510375976562e-05s
INFO | --- Analysis for olac took 131.20315861701965s
Availability | SPARQL endpoint availability check for OLiA took 4.410743713378906e-05s
Availability | VoID file availability check for OLiA took 0.0007634162902832031s
Completeness | Calculation of interlinking completeness for OLiA took 0.36304163932800293s
Reputation | Calculation of the PageRank for OLiA took 0.021149635314941406s
Interlinking | Calculation of Degree of Connection for OLiA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.0001246929168701172s
Believability | Calculation of trust value for OLiA took 1.2636184692382812e-05s
INFO | --- Analysis for olia took 164.88642621040344s
Availability | SPARQL endpoint availability check for OLiA Discourse took 5.793571472167969e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0008139610290527344s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.34059619903564453s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.02166008949279785s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.6253204345703125e-05s
Believability | Calculation of trust value for OLiA Discourse took 1.9550323486328125e-05s
INFO | --- Analysis for olia-discourse took 80.62024807929993s
Availability | SPARQL endpoint availability check for Open Land Use took 0.34024739265441895s
Availability | VoID file availability check for Open Land Use took 0.0003459453582763672s
Extra | Recovery of all triples for Open Land Use took 108.85191679000854s
Performance | Total latancy measurement for Open Land Use took 0.9522223472595215s
Amount of data | Number of triples check for Open Land Use took 8.904619693756104s
Interoperability | New terms check for Open Land Use took 14.174215316772461s
Versatility | Languages check for Open Land Use took 300.1510536670685s
Interpretability | Number of blank nodes check for Open Land Use took 2.1186139583587646s
Interpretability | RDF structures check for Open Land Use took 0.39279699325561523s
Versatility | Serialization formats check for Open Land Use took 9.709112405776978s
Availability | RDF dump link check for Open Land Use took 0.2790415287017822s
License | MR license check for Open Land Use took 0.6140670776367188s
License | HR license check for Open Land Use took 300.22379446029663s
Amount of data | Number of property check for Open Land Use took 0.22487401962280273s
Understandability | Number of label check for Open Land Use took 3.1585094928741455s
Understandability | URI regex check for Open Land Use took 1.2921853065490723s
Understandability | Vocabs check for Open Land Use took 0.6883137226104736s
Verifiability | Authors check for Open Land Use took 0.1869373321533203s
Verifiability | Publishers check for Open Land Use took 0.2418508529663086s
Performance | Throughput check for Open Land Use took 10.949015855789185s
Amount of data | Check the number of entities for Open Land Use took 0.00011372566223144531s
Verifiability | Contribs. check for Open Land Use took 0.19077086448669434s
Interlinking | sameAs chians check for Open Land Use took 0.21645665168762207s
Interlinking | skos check for Open Land Use took 0.4748115539550781s
Interlinking | skos check for Open Land Use took 0.4331471920013428s
Timeliness | dataset update frequency check for Open Land Use took 6.506760835647583s
Currency | Creation date check for Open Land Use took 0.5280764102935791s
Currency | Modification date check for Open Land Use took 0.2506401538848877s
Rep.Conc. | URIs length for Open Land Use took 150.44224071502686s
Interoperability | New vocabularies check for Open Land Use took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.19560480117797852s
Accuracy | Check Functional Property for Open Land Use took 0.37555360794067383s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.33786773681640625s
Accuracy | Check Empty annotation labels for Open Land Use took 39.25715160369873s
Accuracy | Check White space in annotation for Open Land Use took 2.71327543258667s
Accuracy | Check Datatype consistency for Open Land Use took 2.685980796813965s
Consistency | Disjoint class check for Open Land Use took 0.21163654327392578s
Consistency | Check Misplaced properties for Open Land Use took 87.29597449302673s
Consistency | Misplaced classes for Open Land Use took 8.49296259880066s
Consistency | Check Ontology hijacking for Open Land Use took 33.903966426849365s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.5171551704406738s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 88.53430438041687s
Conciseness | Check Extensional conciseness for Open Land Use took 2.8028318881988525s
Conciseness | Check Intensional conciseness for Open Land Use took 0.4767143726348877s
Security | Sign check for Open Land Use took 1.6865429878234863s
Availability | Check URIs Dereferenciability for Open Land Use took 10.237332344055176s
Completeness | Calculation of interlinking completeness for Open Land Use took 25.03012251853943s
Reputation | Calculation of the PageRank for Open Land Use took 0.02120685577392578s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 4.2438507080078125e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Land Use took 1.239776611328125e-05s
INFO | --- Analysis for OLU took 2413.101506948471s
Availability | SPARQL endpoint availability check for OmegaWiki took 6.246566772460938e-05s
Availability | VoID file availability check for OmegaWiki took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.3265955448150635s
Reputation | Calculation of the PageRank for OmegaWiki took 0.02178668975830078s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 3.886222839355469e-05s
Believability | Calculation of trust value for OmegaWiki took 1.239776611328125e-05s
INFO | --- Analysis for omegawiki took 164.12740778923035s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.6369266510009766s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.31587886810302734s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.020982980728149414s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 4.9591064453125e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 1.5974044799804688e-05s
INFO | --- Analysis for omwn-als took 129.50177454948425s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.26827549934387207s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.387129545211792s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0218658447265625s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 5.221366882324219e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 1.3589859008789062e-05s
INFO | --- Analysis for omwn-arb took 138.49695920944214s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.2573411464691162s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 30.655295610427856s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.022611618041992188s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 4.220008850097656e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-bul took 105.24431562423706s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2633671760559082s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.3511621952056885s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.02165699005126953s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0011420249938964844s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 6.318092346191406e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-cow took 127.36187148094177s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.3080580234527588s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 28.188258171081543s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0209195613861084s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 4.649162292480469e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-06s
INFO | --- Analysis for omwn-cwn took 113.98855948448181s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.2571291923522949s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 30.569932460784912s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.021125316619873047s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-dan took 108.73439741134644s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.2990446090698242s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.32871222496032715s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.02112102508544922s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 4.363059997558594e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-ell took 133.74285674095154s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.28827333450317383s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.321666955947876s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.02111983299255371s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0008077621459960938s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 4.315376281738281e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-eng took 131.28711080551147s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.26936864852905273s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 27.356685400009155s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.021237850189208984s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 5.173683166503906e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-fas took 126.83160400390625s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2441258430480957s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.29195189476013184s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.02124190330505371s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.76837158203125e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-fin took 82.85247278213501s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.2657487392425537s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 25.11620545387268s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.021088361740112305s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 4.482269287109375e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-fra took 79.45335078239441s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.263263463973999s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 25.563408613204956s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.02118968963623047s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 4.220008850097656e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-heb took 156.6513547897339s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.27121615409851074s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0003008842468261719s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 24.788016319274902s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.02145838737487793s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 5.340576171875e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
INFO | --- Analysis for omwn-hrv took 145.92760944366455s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.3327620029449463s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.3111538887023926s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.021118640899658203s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 4.601478576660156e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-isl took 25.69731831550598s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.2616276741027832s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 24.92819333076477s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.021047115325927734s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 4.982948303222656e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-ita took 81.82193517684937s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.31574153900146484s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 27.815718412399292s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.02089834213256836s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 4.1961669921875e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.8358230590820312e-05s
INFO | --- Analysis for omwn-iwn took 76.7755777835846s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.2693765163421631s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.3113884925842285s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.02184605598449707s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0009450912475585938s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 4.7206878662109375e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-jpn took 34.587528705596924s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.2806243896484375s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.35706472396850586s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.021411657333374023s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 4.220008850097656e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-mcr took 106.98826813697815s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2771282196044922s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 28.30378556251526s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.02124500274658203s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 5.316734313964844e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-msa took 98.94226360321045s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.3006317615509033s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 31.490528345108032s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.021090030670166016s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 5.435943603515625e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-nld took 85.33342289924622s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.3104715347290039s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 27.218783855438232s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.021028518676757812s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 4.744529724121094e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.3828277587890625e-05s
INFO | --- Analysis for omwn-nor took 154.0158612728119s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2962214946746826s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.00054931640625s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.29529356956481934s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.021611928939819336s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 4.458427429199219e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-pol took 54.09881114959717s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.30850744247436523s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 23.52146887779236s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.021419286727905273s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0008189678192138672s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 5.054473876953125e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-por took 102.44466519355774s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2524850368499756s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 28.328491687774658s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.020873069763183594s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 4.6253204345703125e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-ron took 131.81754207611084s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.26193809509277344s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.00030541419982910156s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.3331425189971924s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.021502017974853516s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 4.38690185546875e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-slk took 131.92249131202698s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.3427565097808838s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.3025987148284912s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.021251678466796875s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 5.173683166503906e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
INFO | --- Analysis for omwn-slv took 52.715397119522095s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.28786158561706543s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.48693251609802246s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.02089381217956543s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 5.626678466796875e-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 208.32707047462463s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.30411601066589355s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0024111270904541016s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.30017781257629395s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.021435260772705078s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 5.459785461425781e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-tha took 94.71186137199402s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 3.9614760875701904s
Availability | VoID file availability check for OntoBeef Domain took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.3053710460662842s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020936012268066406s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 5.14984130859375e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.0251998901367188e-05s
INFO | --- Analysis for ontobeef-domain took 178.13405179977417s
Availability | SPARQL endpoint availability check for Ontos News Portal took 9.465217590332031e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.29731249809265137s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.021173477172851562s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 0.0001010894775390625s
Believability | Calculation of trust value for Ontos News Portal took 7.62939453125e-06s
INFO | --- Analysis for ontos-news-portal took 39.76664900779724s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 9.131431579589844e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0003292560577392578s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.30234360694885254s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.02117300033569336s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 4.38690185546875e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 1.2636184692382812e-05s
INFO | --- Analysis for ookaboo-rdf-dump took 81.65167570114136s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 0.0001506805419921875s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0007123947143554688s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.3355743885040283s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.021091699600219727s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 4.744529724121094e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 8.344650268554688e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 186.475435256958s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0003936290740966797s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.2981395721435547s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.02346944808959961s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 3.7670135498046875e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 1.3589859008789062e-05s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 74.29225993156433s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 0.00010371208190917969s
Availability | VoID file availability check for Open Data Euskadi took 0.0007381439208984375s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.34537672996520996s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.0211637020111084s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 6.151199340820312e-05s
Believability | Calculation of trust value for Open Data Euskadi took 9.5367431640625e-06s
INFO | --- Analysis for open-data-euskadi took 140.64316749572754s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 6.079673767089844e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.8908438682556152s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.44903993606567383s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.021196603775024414s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00011968612670898438s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 1.0728836059570312e-05s
INFO | --- Analysis for open-data-risp took 55.46029353141785s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.24199151992797852s
Availability | VoID file availability check for Open Data Thesaurus took 0.0007143020629882812s
Extra | Recovery of all triples for Open Data Thesaurus took 1.390718936920166s
Performance | Total latancy measurement for Open Data Thesaurus took 0.4609501361846924s
Amount of data | Number of triples check for Open Data Thesaurus took 0.12285494804382324s
Interoperability | New terms check for Open Data Thesaurus took 1.4676289558410645s
Versatility | Languages check for Open Data Thesaurus took 0.1177518367767334s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.12100696563720703s
Security | Check HTTPS for Open Data Thesaurus took 0.32527780532836914s
Interpretability | RDF structures check for Open Data Thesaurus took 0.12327694892883301s
Versatility | Serialization formats check for Open Data Thesaurus took 0.10780954360961914s
Availability | RDF dump link check for Open Data Thesaurus took 1.1007211208343506s
License | MR license check for Open Data Thesaurus took 0.12198710441589355s
License | HR license check for Open Data Thesaurus took 0.09415817260742188s
Amount of data | Number of property check for Open Data Thesaurus took 0.1143949031829834s
Understandability | Number of label check for Open Data Thesaurus took 0.12293100357055664s
Understandability | URI regex check for Open Data Thesaurus took 0.16711187362670898s
Understandability | Vocabs check for Open Data Thesaurus took 0.11421012878417969s
Verifiability | Authors check for Open Data Thesaurus took 0.10729765892028809s
Verifiability | Publishers check for Open Data Thesaurus took 0.10657906532287598s
Performance | Throughput check for Open Data Thesaurus took 10.498066663742065s
Amount of data | Check the number of entities for Open Data Thesaurus took 5.125999450683594e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.12198448181152344s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.12182497978210449s
Interlinking | skos check for Open Data Thesaurus took 0.11594462394714355s
Interlinking | skos check for Open Data Thesaurus took 0.08720755577087402s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.0885624885559082s
Currency | Creation date check for Open Data Thesaurus took 0.1789999008178711s
Currency | Modification date check for Open Data Thesaurus took 0.2051560878753662s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.4497814178466797s
Interoperability | New vocabularies check for Open Data Thesaurus took 0.6749048233032227s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.11546206474304199s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.09624433517456055s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.09485554695129395s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.1922624111175537s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.001134634017944336s
Consistency | Disjoint class check for Open Data Thesaurus took 0.09524393081665039s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.16747307777404785s
Consistency | Misplaced classes for Open Data Thesaurus took 0.08720660209655762s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.5091586112976074s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.4504787921905518s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.0001647472381591797s
Security | Sign check for Open Data Thesaurus took 0.07925891876220703s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 23.855995893478394s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.0208590030670166s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 9.059906005859375e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 0.5740995407104492s
Believability | Calculation of trust value for Open Data Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for open-data-thesaurus took 177.07776641845703s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 20.216612577438354s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.0007884502410888672s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 24.554657220840454s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.021417856216430664s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0010914802551269531s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 5.0067901611328125e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 1.7404556274414062e-05s
INFO | --- Analysis for open-data-tor-vergata took 291.2085611820221s
Availability | SPARQL endpoint availability check for Open Election Data Project took 9.083747863769531e-05s
Availability | VoID file availability check for Open Election Data Project took 0.000736236572265625s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.32074785232543945s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.021060943603515625s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 7.510185241699219e-05s
Believability | Calculation of trust value for Open Election Data Project took 2.2172927856445312e-05s
INFO | --- Analysis for open-election-data-project took 123.37727665901184s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 5.467962741851807s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 22.513421058654785s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02116680145263672s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 0.00010156631469726562s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 1.0013580322265625e-05s
INFO | --- Analysis for open-energy-info-wiki took 112.75631785392761s
Availability | SPARQL endpoint availability check for Open Library took 4.4345855712890625e-05s
Availability | VoID file availability check for Open Library took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for Open Library took 0.3347620964050293s
Reputation | Calculation of the PageRank for Open Library took 0.020884037017822266s
Interlinking | Calculation of Degree of Connection for Open Library took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Library took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Open Library took 7.271766662597656e-05s
Believability | Calculation of trust value for Open Library took 1.1205673217773438e-05s
INFO | --- Analysis for open-library took 32.94981598854065s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.6030614376068115s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0005702972412109375s
Extra | Recovery of all triples for Open Land Use @PSNC took 102.63827991485596s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.9999709129333496s
Amount of data | Number of triples check for Open Land Use @PSNC took 9.189188957214355s
Interoperability | New terms check for Open Land Use @PSNC took 14.294190645217896s
Versatility | Languages check for Open Land Use @PSNC took 300.20213055610657s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 2.235917568206787s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.304462194442749s
Versatility | Serialization formats check for Open Land Use @PSNC took 8.744401454925537s
Availability | RDF dump link check for Open Land Use @PSNC took 0.2657439708709717s
License | MR license check for Open Land Use @PSNC took 0.4799067974090576s
License | HR license check for Open Land Use @PSNC took 300.21286511421204s
Amount of data | Number of property check for Open Land Use @PSNC took 0.1931145191192627s
Understandability | Number of label check for Open Land Use @PSNC took 3.3488619327545166s
Understandability | URI regex check for Open Land Use @PSNC took 0.860173225402832s
Understandability | Vocabs check for Open Land Use @PSNC took 0.6921036243438721s
Verifiability | Authors check for Open Land Use @PSNC took 0.20596575736999512s
Verifiability | Publishers check for Open Land Use @PSNC took 0.24596095085144043s
Performance | Throughput check for Open Land Use @PSNC took 11.355809450149536s
Amount of data | Check the number of entities for Open Land Use @PSNC took 6.222724914550781e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.18352293968200684s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.19958806037902832s
Interlinking | skos check for Open Land Use @PSNC took 0.43131279945373535s
Interlinking | skos check for Open Land Use @PSNC took 0.4271399974822998s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 3.984692096710205s
Currency | Creation date check for Open Land Use @PSNC took 0.48563504219055176s
Currency | Modification date check for Open Land Use @PSNC took 0.257671594619751s
Rep.Conc. | URIs length for Open Land Use @PSNC took 152.65873956680298s
Interoperability | New vocabularies check for Open Land Use @PSNC took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.1995246410369873s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.38916802406311035s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.4154825210571289s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 35.64956998825073s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.715242624282837s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.675794839859009s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.1944124698638916s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 87.01282525062561s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.423949480056763s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 31.85823154449463s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.494983434677124s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 87.46532917022705s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.811415910720825s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.5823934078216553s
Security | Sign check for Open Land Use @PSNC took 1.254509687423706s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 9.939325332641602s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 22.884153604507446s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.02349114418029785s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 3.24249267578125e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0010936260223388672s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 4.5299530029296875e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.2636184692382812e-05s
INFO | --- Analysis for Open_Land_Use took 2456.755485534668s
Availability | SPARQL endpoint availability check for flyatlas took 0.9879424571990967s
Availability | VoID file availability check for flyatlas took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for flyatlas took 0.37319517135620117s
Reputation | Calculation of the PageRank for flyatlas took 0.022837162017822266s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.600120544433594e-05s
Believability | Calculation of trust value for flyatlas took 1.2636184692382812e-05s
INFO | --- Analysis for openbiomed-flyatlas took 5.5892839431762695s
Availability | SPARQL endpoint availability check for OpenCalais took 0.00015616416931152344s
Availability | VoID file availability check for OpenCalais took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for OpenCalais took 26.712866067886353s
Reputation | Calculation of the PageRank for OpenCalais took 0.021787643432617188s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00012230873107910156s
Believability | Calculation of trust value for OpenCalais took 1.33514404296875e-05s
INFO | --- Analysis for opencalais took 87.85607194900513s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 0.00014901161193847656s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0008199214935302734s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.38248634338378906s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.021178245544433594s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 8.130073547363281e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 5.0067901611328125e-06s
INFO | --- Analysis for opencorporates took 81.49693369865417s
Availability | SPARQL endpoint availability check for OpenCyc took 9.298324584960938e-05s
Availability | VoID file availability check for OpenCyc took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for OpenCyc took 28.914519548416138s
Reputation | Calculation of the PageRank for OpenCyc took 0.021736621856689453s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00011801719665527344s
Believability | Calculation of trust value for OpenCyc took 6.67572021484375e-06s
INFO | --- Analysis for opencyc took 83.24663162231445s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.38283848762512207s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.021270036697387695s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 3.915832996368408s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.601478576660156e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007665157318115234s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 24.00067138671875s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.021578311920166016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 5.364418029785156e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 102.58244562149048s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.00014352798461914062s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.36362218856811523s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.020931243896484375s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 26.998268842697144s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 9.274482727050781e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 23.201913595199585s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.021300554275512695s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 1.9073486328125e-05s
INFO | --- Analysis for opendatacommunities-households-2008 took 105.22331094741821s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.649162292480469e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.3096492290496826s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.021543025970458984s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 76.54419469833374s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 9.34600830078125e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0007772445678710938s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.3147914409637451s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.021099328994750977s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.5497207641601562e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 131.24876070022583s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 9.131431579589844e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 25.595713138580322s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.021404266357421875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0020515918731689453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 5.4836273193359375e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 156.00943994522095s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.6253204345703125e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.3230733871459961s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0215151309967041s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 73.55071830749512s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0001647472381591797s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.00075531005859375s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.3673069477081299s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.021382808685302734s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.839897155761719e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 107.27550554275513s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 9.226799011230469e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.33713769912719727s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.021112442016601562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 138.38499546051025s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 24.69162607192993s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.021375179290771484s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 101.87529873847961s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.5299530029296875e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.33981990814208984s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.02408456802368164s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0009469985961914062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 26.044743537902832s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 5.53131103515625e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.3038492202758789s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.023246288299560547s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 57.84748888015747s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 0.0001049041748046875s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.30347180366516113s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.021179914474487305s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 78.820871591568s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 9.202957153320312e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0006740093231201172s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 25.277353048324585s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.02157115936279297s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 56.89141368865967s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.6253204345703125e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007052421569824219s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 24.85591745376587s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.02140069007873535s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 1.8596649169921875e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 102.72737407684326s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 5.555152893066406e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.30618953704833984s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.02131938934326172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 53.6535370349884s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 9.250640869140625e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0007262229919433594s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.2854127883911133s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.021219253540039062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 5.53131103515625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 55.16734576225281s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.8160552978515625e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 26.729989290237427s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.02134251594543457s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.673004150390625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 158.00332164764404s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 9.226799011230469e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.3551197052001953s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.02129220962524414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 5.173683166503906e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 138.45157623291016s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 9.512901306152344e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0006868839263916016s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.35218095779418945s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.021367549896240234s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 76.32188868522644s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.601478576660156e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.3597850799560547s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.02106928825378418s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 5.269050598144531e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 109.03714895248413s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.792213439941406e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.2953336238861084s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020995378494262695s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0008206367492675781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.792213439941406e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 51.435628175735474s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0001246929168701172s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007483959197998047s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 25.32298994064331s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.021506547927856445s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 5.340576171875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 163.30936241149902s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007405281066894531s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.4007835388183594s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0213775634765625s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 32.05222249031067s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.00013184547424316406s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007884502410888672s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.4132201671600342s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.02149796485900879s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 5.3882598876953125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 98.03825640678406s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 9.465217590332031e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0008263587951660156s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.30310606956481934s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.02100229263305664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0008807182312011719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.935264587402344e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 147.7003996372223s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.00010013580322265625s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0008192062377929688s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.2973783016204834s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.02137923240661621s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 5.364418029785156e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 148.9499373435974s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0001220703125s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 22.14042329788208s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.021234750747680664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 5.245208740234375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 102.26016402244568s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 27.20527410507202s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.021234512329101562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 54.828595876693726s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0001227855682373047s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007579326629638672s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 26.91494846343994s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.02233266830444336s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 5.626678466796875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 137.11059188842773s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.744529724121094e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 25.35012435913086s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.02096414566040039s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.935264587402344e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 158.63068962097168s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 9.775161743164062e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.2998933792114258s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.022377967834472656s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0011136531829833984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 6.246566772460938e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 26.501739740371704s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.893013000488281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.289233922958374s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.02123284339904785s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.364418029785156e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 88.48814034461975s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 9.942054748535156e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.2893948554992676s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.02109241485595703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 154.8222439289093s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.6253204345703125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 23.048543214797974s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.021146774291992188s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 3.2901763916015625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 5.054473876953125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 104.88972616195679s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 9.226799011230469e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 26.065390586853027s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.021239042282104492s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.839897155761719e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 79.17138624191284s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.792213439941406e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 27.075867652893066s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.02126622200012207s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 101.72809076309204s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.3245961666107178s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.02099752426147461s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 75.85262608528137s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 8.106231689453125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0008039474487304688s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 23.199848413467407s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.021242380142211914s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 5.3882598876953125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 93.14242935180664s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 9.202957153320312e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 22.999330759048462s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0215914249420166s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.935264587402344e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 176.2908730506897s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 9.34600830078125e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0008146762847900391s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.28084468841552734s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.021606922149658203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0008552074432373047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 79.08378386497498s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.9591064453125e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0013210773468017578s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.2951970100402832s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.023307323455810547s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0011546611785888672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 5.435943603515625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 128.78238892555237s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 4.142862796783447s
Availability | VoID file availability check for Open Data of Ecuador took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.316727876663208s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.021270036697387695s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 0.00010204315185546875s
Believability | Calculation of trust value for Open Data of Ecuador took 7.3909759521484375e-06s
INFO | --- Analysis for opendataec took 104.32277870178223s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 9.202957153320312e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 23.371774196624756s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.022024869918823242s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0009593963623046875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 6.0558319091796875e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.7881393432617188e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 137.2982189655304s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 5.054473876953125e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.30502796173095703s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.02089071273803711s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 1.2636184692382812e-05s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 51.70850133895874s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 9.417533874511719e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.3021540641784668s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.0211184024810791s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 1.3113021850585938e-05s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 140.51743340492249s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 0.00010585784912109375s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.31295084953308105s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.021219253540039062s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 1.1682510375976562e-05s
INFO | --- Analysis for opendatascotland-simd-education-rank took 76.09090161323547s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.839897155761719e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.32193470001220703s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.021230220794677734s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.2874603271484375e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 88.51747465133667s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 4.601478576660156e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.34779930114746094s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.02180957794189453s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 4.887580871582031e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 1.239776611328125e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 148.45914268493652s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 0.00016760826110839844s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.3275563716888428s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02156996726989746s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 1.33514404296875e-05s
INFO | --- Analysis for opendatascotland-simd-health-rank took 73.43287992477417s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 9.369850158691406e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.3515145778656006s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.021283388137817383s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 1.33514404296875e-05s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 99.23211288452148s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 9.989738464355469e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.29927682876586914s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.02107858657836914s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 76.99060463905334s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 31.31394934654236s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 23.074574947357178s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020990371704101562s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.1205673217773438e-05s
INFO | --- Analysis for openlink-lod-cache took 134.41577625274658s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 6.008148193359375e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.3343167304992676s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.021308183670043945s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 0.00010061264038085938s
Believability | Calculation of trust value for openlinksw dataspaces took 1.2874603271484375e-05s
INFO | --- Analysis for openlinksw-dataspaces took 32.303215742111206s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 0.0001373291015625s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.3016667366027832s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020956754684448242s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.870529174804688e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 4.76837158203125e-06s
INFO | --- Analysis for openlylocal took 31.12983775138855s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.557260274887085s
Availability | VoID file availability check for OpenMobileNetwork took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 24.255325078964233s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.023143768310546875s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 8.749961853027344e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 1.3113021850585938e-05s
INFO | --- Analysis for openmobilenetwork took 52.18154454231262s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.6790342330932617s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0007278919219970703s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.2915012836456299s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.942054748535156e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 49.655081033706665s
Availability | SPARQL endpoint availability check for oreilly took 9.012222290039062e-05s
Availability | VoID file availability check for oreilly took 0.0007684230804443359s
Completeness | Calculation of interlinking completeness for oreilly took 0.323650598526001s
Reputation | Calculation of the PageRank for oreilly took 0.021192312240600586s
Interlinking | Calculation of Degree of Connection for oreilly took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for oreilly took 5.269050598144531e-05s
Believability | Calculation of trust value for oreilly took 1.1920928955078125e-05s
INFO | --- Analysis for oreilly took 129.96099400520325s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.40437388420105s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.29980897903442383s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.023037195205688477s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.719329833984375e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 1.2874603271484375e-05s
INFO | --- Analysis for Organchem-Data took 81.92907333374023s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.04721784591674805s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.00032019615173339844s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.3950366973876953s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.021105289459228516s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 7.605552673339844e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.2636184692382812e-05s
INFO | --- Analysis for organic-edunet took 80.64575576782227s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.45642685890197754s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0006158351898193359s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 6.254161596298218s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.7280385494232178s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.1660935878753662s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.7069711685180664s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 5.595116853713989s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.16254973411560059s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.3317742347717285s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.15732836723327637s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.14355754852294922s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.14138436317443848s
License | HR license check for Open Research Knowledge Graph (ORKG) took 3.1608011722564697s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.15972566604614258s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.15926432609558105s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.2889695167541504s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.16880416870117188s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.1235666275024414s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.14452815055847168s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.602842807769775s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 7.581710815429688e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.15306496620178223s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.16512537002563477s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.1454479694366455s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.1577136516571045s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.14720630645751953s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.3335909843444824s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.34737324714660645s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 3.9565463066101074s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.12862920761108398s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.20423102378845215s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.20736455917358398s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 2.3686270713806152s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.30732083320617676s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.2944352626800537s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.2131800651550293s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.2741210460662842s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.897836446762085s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 3.297520160675049s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.4119744300842285s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.169306516647339s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.3017258644104004s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.15311932563781738s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.16593194007873535s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 1976.7609434127808s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 23.83756399154663s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.021750211715698242s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 2.9802322387695312e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 2.384185791015625e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.2636184692382812e-05s
INFO | --- Analysis for orkg took 2305.2929739952087s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.0316736698150635s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0007572174072265625s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.29692745208740234s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.0212709903717041s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 0.00010204315185546875s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 7.62939453125e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 101.45401549339294s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.580786943435669s
Availability | VoID file availability check for OSM Semantic Network took 0.0013039112091064453s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.31351542472839355s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.021142005920410156s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 4.2438507080078125e-05s
Believability | Calculation of trust value for OSM Semantic Network took 1.239776611328125e-05s
INFO | --- Analysis for osm-semantic-network took 84.79547142982483s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 60.06342267990112s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.29784488677978516s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.02155137062072754s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.4332275390625e-05s
Believability | Calculation of trust value for Open Transport Map @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for OTM took 175.6133632659912s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.124641418457031e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.0007607936859130859s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 28.63332223892212s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.021303653717041016s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 3.886222839355469e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 8.344650268554688e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 131.4756920337677s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 2.587503671646118s
Availability | VoID file availability check for Pali English Lexicon took 0.00040268898010253906s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.3100881576538086s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.02309417724609375s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 4.172325134277344e-05s
Believability | Calculation of trust value for Pali English Lexicon took 1.1444091796875e-05s
INFO | --- Analysis for pali-english-lexicon took 115.97903656959534s
Availability | SPARQL endpoint availability check for PanLex took 1.7683923244476318s
Availability | VoID file availability check for PanLex took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for PanLex took 23.51607370376587s
Reputation | Calculation of the PageRank for PanLex took 0.02112746238708496s
Interlinking | Calculation of Degree of Connection for PanLex took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0008080005645751953s
Interlinking | Calculation of Clustering coefficient for PanLex took 8.702278137207031e-05s
Believability | Calculation of trust value for PanLex took 1.2636184692382812e-05s
INFO | --- Analysis for panlex took 114.41481113433838s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.57763671875e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 26.129436254501343s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.021197080612182617s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 4.696846008300781e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.2874603271484375e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 88.95001220703125s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.12099337577819824s
Availability | VoID file availability check for patents.data.gov.uk took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.38684892654418945s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.021121978759765625s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 5.435943603515625e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 6.4373016357421875e-06s
INFO | --- Analysis for patents-data-gov-uk took 53.351747035980225s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.76837158203125e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0007348060607910156s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 28.473690032958984s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.021126270294189453s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 5.221366882324219e-05s
Believability | Calculation of trust value for PDEV-Lemon took 7.62939453125e-06s
INFO | --- Analysis for pdev-lemon took 131.71084594726562s
Availability | SPARQL endpoint availability check for pdevlemon took 4.5299530029296875e-05s
Availability | VoID file availability check for pdevlemon took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for pdevlemon took 26.577791929244995s
Reputation | Calculation of the PageRank for pdevlemon took 0.021416187286376953s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.409385681152344e-05s
Believability | Calculation of trust value for pdevlemon took 1.239776611328125e-05s
INFO | --- Analysis for pdevlemon took 130.54536628723145s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 5.173683166503906e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0008537769317626953s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.33754706382751465s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020973920822143555s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 9.822845458984375e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 1.2159347534179688e-05s
INFO | --- Analysis for periodo took 152.40098905563354s
Availability | SPARQL endpoint availability check for Personal_Homepages took 6.341934204101562e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.28208088874816895s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.02286815643310547s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.0004279613494873047s
Believability | Calculation of trust value for Personal_Homepages took 7.152557373046875e-06s
INFO | --- Analysis for personal-homepages took 73.02375817298889s
Availability | SPARQL endpoint availability check for Ontology of University People took 0.00017595291137695312s
Availability | VoID file availability check for Ontology of University People took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.3197317123413086s
Reputation | Calculation of the PageRank for Ontology of University People took 0.02171158790588379s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 3.62396240234375e-05s
Believability | Calculation of trust value for Ontology of University People took 7.152557373046875e-06s
INFO | --- Analysis for PersonOnto took 55.37200212478638s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 3.708359479904175s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 24.14335536956787s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02189779281616211s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.2874603271484375e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 7.867813110351562e-06s
INFO | --- Analysis for PFKHS took 167.02485942840576s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 2.436746835708618s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007624626159667969s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.32398366928100586s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.021228790283203125s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3113021850585938e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.239776611328125e-05s
INFO | --- Analysis for PFRPPH took 31.41781449317932s
Availability | SPARQL endpoint availability check for PGxLOD took 30.256316900253296s
Availability | VoID file availability check for PGxLOD took 0.0007221698760986328s
Completeness | Calculation of interlinking completeness for PGxLOD took 27.98071599006653s
Reputation | Calculation of the PageRank for PGxLOD took 0.02128434181213379s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 4.57763671875e-05s
Believability | Calculation of trust value for PGxLOD took 1.3828277587890625e-05s
INFO | --- Analysis for PGxLOD took 214.65419840812683s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.9095499515533447s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0003540515899658203s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.3131392002105713s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.02109384536743164s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 4.291534423828125e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 7.3909759521484375e-06s
INFO | --- Analysis for phoible took 86.33956575393677s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 7.748603820800781e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.00075531005859375s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 33.01711106300354s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.021470069885253906s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.743171691894531e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 1.2159347534179688e-05s
INFO | --- Analysis for PISM took 112.30968761444092s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.553794860839844e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 30.493587493896484s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.021979808807373047s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 9.5367431640625e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 1.2159347534179688e-05s
INFO | --- Analysis for planetdata-project-wiki took 102.03029084205627s
Availability | SPARQL endpoint availability check for digitized plant specimen took 0.9918506145477295s
Availability | VoID file availability check for digitized plant specimen took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.2987961769104004s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.021450519561767578s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 3.0040740966796875e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.001253366470336914s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 0.00012111663818359375s
Believability | Calculation of trust value for digitized plant specimen took 1.239776611328125e-05s
INFO | --- Analysis for plant-specimen took 69.49038791656494s
Availability | SPARQL endpoint availability check for Pleiades took 9.059906005859375e-05s
Availability | VoID file availability check for Pleiades took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Pleiades took 22.940749645233154s
Reputation | Calculation of the PageRank for Pleiades took 0.021401166915893555s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Pleiades took 9.036064147949219e-05s
Believability | Calculation of trust value for Pleiades took 1.3113021850585938e-05s
INFO | --- Analysis for pleiades took 81.2602322101593s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 8.702278137207031e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.28835201263427734s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.02382373809814453s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 4.267692565917969e-05s
Believability | Calculation of trust value for podorozhnyk.com took 7.867813110351562e-06s
INFO | --- Analysis for podorozhnyk took 79.98708367347717s
Availability | SPARQL endpoint availability check for Poképédia took 5.7220458984375e-05s
Availability | VoID file availability check for Poképédia took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2946352958679199s
Reputation | Calculation of the PageRank for Poképédia took 0.02139139175415039s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Poképédia took 8.58306884765625e-05s
Believability | Calculation of trust value for Poképédia took 1.1920928955078125e-05s
INFO | --- Analysis for pokepedia-fr took 96.01613092422485s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.00010061264038085938s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.28519582748413086s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.021308422088623047s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0008397102355957031s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 8.988380432128906e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.239776611328125e-05s
INFO | --- Analysis for polymath-virtual-library took 166.8644528388977s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2799704074859619s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0004928112030029297s
Extra | Recovery of all triples for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 12.611737728118896s
Performance | Total latancy measurement for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.6210284233093262s
Amount of data | Number of triples check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.6862490177154541s
Interoperability | New terms check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6739673614501953s
Versatility | Languages check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6561319828033447s
Interpretability | Number of blank nodes check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.423778772354126s
Interpretability | RDF structures check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12818646430969238s
Versatility | Serialization formats check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11941671371459961s
Availability | RDF dump link check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11729598045349121s
License | MR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12537264823913574s
License | HR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.5674164295196533s
Amount of data | Number of property check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12421107292175293s
Understandability | Number of label check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.16174077987670898s
Understandability | URI regex check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2413311004638672s
Understandability | Vocabs check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1325838565826416s
Verifiability | Authors check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13247942924499512s
Verifiability | Publishers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11648893356323242s
Performance | Throughput check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.685092687606812s
Amount of data | Check the number of entities for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 7.414817810058594e-05s
Verifiability | Contribs. check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12477254867553711s
Interlinking | sameAs chians check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12333369255065918s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12389826774597168s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11624002456665039s
Timeliness | dataset update frequency check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12447643280029297s
Currency | Creation date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2394392490386963s
Currency | Modification date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.23986458778381348s
Rep.Conc. | URIs length for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.9260759353637695s
Interoperability | New vocabularies check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12247943878173828s
Accuracy | Check Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12925481796264648s
Accuracy | Check Inverse Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11658859252929688s
Accuracy | Check Empty annotation labels for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.1680009365081787s
Accuracy | Check White space in annotation for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.19929981231689453s
Accuracy | Check Datatype consistency for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.7872557640075684s
Consistency | Disjoint class check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12452340126037598s
Consistency | Check Misplaced properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.893486738204956s
Consistency | Check Ontology hijacking for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.539663314819336s
Consistency | Check Invalid usage of undefined classes for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.3839221000671387s
Consistency | Check Invalid usage of undefined properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.206799030303955s
Conciseness | Check Extensional conciseness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.5131781101226807s
Security | Sign check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11435627937316895s
Availability | Check URIs Dereferenciability for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 4797.898777246475s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 25.7367684841156s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0248110294342041s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.0279159545898438e-05s
Interoperability | Check the re-using of existing vocabs for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 8.106231689453125e-05s
INFO | --- Analysis for portuguese_prisons_releases took 5099.834908485413s
Availability | SPARQL endpoint availability check for prefix.cc took 5.364418029785156e-05s
Availability | VoID file availability check for prefix.cc took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for prefix.cc took 24.2011981010437s
Reputation | Calculation of the PageRank for prefix.cc took 0.02108907699584961s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 4.673004150390625e-05s
Believability | Calculation of trust value for prefix.cc took 5.221366882324219e-05s
INFO | --- Analysis for prefix-cc took 101.29286122322083s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.6433143615722656s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0007770061492919922s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.3085644245147705s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.021157026290893555s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 5.412101745605469e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.2636184692382812e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 85.77183938026428s
Availability | SPARQL endpoint availability check for PreLex took 7.0529468059539795s
Availability | VoID file availability check for PreLex took 0.0008251667022705078s
Completeness | Calculation of interlinking completeness for PreLex took 0.319857120513916s
Reputation | Calculation of the PageRank for PreLex took 0.021608352661132812s
Interlinking | Calculation of Degree of Connection for PreLex took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for PreLex took 8.273124694824219e-05s
Believability | Calculation of trust value for PreLex took 1.3113021850585938e-05s
INFO | --- Analysis for prelex took 95.65395021438599s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.076821804046631s
Availability | VoID file availability check for Prelinger Archives took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 23.387293100357056s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020882129669189453s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.2901763916015625e-05s
Believability | Calculation of trust value for Prelinger Archives took 1.0728836059570312e-05s
INFO | --- Analysis for prelinger_archives took 86.32086873054504s
Availability | SPARQL endpoint availability check for PreMOn took 0.5368618965148926s
Availability | VoID file availability check for PreMOn took 0.000823974609375s
Completeness | Calculation of interlinking completeness for PreMOn took 24.330438137054443s
Reputation | Calculation of the PageRank for PreMOn took 0.02141857147216797s
Interlinking | Calculation of Degree of Connection for PreMOn took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for PreMOn took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for PreMOn took 6.198883056640625e-05s
Believability | Calculation of trust value for PreMOn took 1.3113021850585938e-05s
INFO | --- Analysis for premon took 128.42856287956238s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 7.867813110351562e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.2945563793182373s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.021303653717041016s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.00089263916015625s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 7.462501525878906e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 1.2636184692382812e-05s
INFO | --- Analysis for princeton-library-findingaids took 126.80769324302673s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.6421711444854736s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0007488727569580078s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 23.628053188323975s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.02128314971923828s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 4.3392181396484375e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 1.3589859008789062e-05s
INFO | --- Analysis for PrinParLat took 202.23866438865662s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.44291186332702637s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 24.86880850791931s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.021503686904907227s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 9.799003601074219e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.239776611328125e-05s
INFO | --- Analysis for printed-book-auction-catalogues took 136.06406354904175s
Availability | SPARQL endpoint availability check for Prior Panel took 9.489059448242188e-05s
Availability | VoID file availability check for Prior Panel took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.2916076183319092s
Reputation | Calculation of the PageRank for Prior Panel took 0.021490097045898438s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 5.030632019042969e-05s
Believability | Calculation of trust value for Prior Panel took 1.2874603271484375e-05s
INFO | --- Analysis for Prior_Panel took 197.11151838302612s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 4.315376281738281e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.3072540760040283s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.021314620971679688s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 3.218650817871094e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 1.33514404296875e-05s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 125.10270357131958s
Availability | SPARQL endpoint availability check for ProductDB took 0.7398526668548584s
Availability | VoID file availability check for ProductDB took 0.0008480548858642578s
Completeness | Calculation of interlinking completeness for ProductDB took 0.2916684150695801s
Reputation | Calculation of the PageRank for ProductDB took 0.021105289459228516s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.939338684082031e-05s
Believability | Calculation of trust value for ProductDB took 1.2636184692382812e-05s
INFO | --- Analysis for productdb took 99.15558910369873s
Availability | SPARQL endpoint availability check for Product Types Ontology took 0.0001499652862548828s
Availability | VoID file availability check for Product Types Ontology took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.30233263969421387s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.02124762535095215s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 8.0108642578125e-05s
Believability | Calculation of trust value for Product Types Ontology took 1.52587890625e-05s
INFO | --- Analysis for productontology took 128.09913778305054s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 0.00011014938354492188s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.3352992534637451s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.023229122161865234s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.0001125335693359375s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.3589859008789062e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 90.27931141853333s
Availability | SPARQL endpoint availability check for provenanceweb took 0.14234590530395508s
Availability | VoID file availability check for provenanceweb took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.31397104263305664s
Reputation | Calculation of the PageRank for provenanceweb took 0.021340131759643555s
Interlinking | Calculation of Degree of Connection for provenanceweb took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 8.749961853027344e-05s
Believability | Calculation of trust value for provenanceweb took 1.2874603271484375e-05s
INFO | --- Analysis for provenanceweb took 124.80346131324768s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 9.72747802734375e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.7495417594909668s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2899484634399414s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.021479368209838867s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00011587142944335938s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.1920928955078125e-05s
INFO | --- Analysis for proyectoapadrina took 110.53392839431763s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.06696057319641s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0009160041809082031s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.28243112564086914s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.02137303352355957s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 6.508827209472656e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 9.059906005859375e-06s
INFO | --- Analysis for pscs-catalogue took 242.31595468521118s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 9.107589721679688e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 26.91761350631714s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.021231889724731445s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 9.322166442871094e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 1.2636184692382812e-05s
INFO | --- Analysis for psh-subject-headings took 133.68919491767883s
Availability | SPARQL endpoint availability check for Depression took 0.5624415874481201s
Availability | VoID file availability check for Depression took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Depression took 0.3006875514984131s
Reputation | Calculation of the PageRank for Depression took 0.02103447914123535s
Interlinking | Calculation of Degree of Connection for Depression took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Depression took 3.409385681152344e-05s
Believability | Calculation of trust value for Depression took 1.1920928955078125e-05s
INFO | --- Analysis for Psychology took 50.58989906311035s
Availability | SPARQL endpoint availability check for PubChem RDF took 4.291534423828125e-05s
Availability | VoID file availability check for PubChem RDF took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.29273152351379395s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020972013473510742s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.553794860839844e-05s
Believability | Calculation of trust value for PubChem RDF took 1.239776611328125e-05s
INFO | --- Analysis for PubChem_RDF took 86.5777735710144s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 6.437941312789917s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.2907834053039551s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.021493196487426758s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 3.409385681152344e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 1.239776611328125e-05s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 115.77719640731812s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 60.04876446723938s
Availability | VoID file availability check for Public Spending in Greece took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.40821385383605957s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.021643638610839844s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 9.512901306152344e-05s
Believability | Calculation of trust value for Public Spending in Greece took 8.58306884765625e-06s
INFO | --- Analysis for public-spending-in-greece took 225.78234338760376s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 9.131431579589844e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.33180856704711914s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.02092909812927246s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 3.62396240234375e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 1.2159347534179688e-05s
INFO | --- Analysis for publications-of-charles-university-in-prague took 98.97159242630005s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.23659896850585938s
Availability | VoID file availability check for Publications Office Authority tables took 0.0007236003875732422s
Extra | Recovery of all triples for Publications Office Authority tables took 182.6159987449646s
Performance | Total latancy measurement for Publications Office Authority tables took 0.5667784214019775s
Amount of data | Number of triples check for Publications Office Authority tables took 48.46766138076782s
Interoperability | New terms check for Publications Office Authority tables took 69.05199146270752s
Versatility | Languages check for Publications Office Authority tables took 300.12909960746765s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 58.28228807449341s
Security | Check HTTPS for Publications Office Authority tables took 0.31615447998046875s
Interpretability | RDF structures check for Publications Office Authority tables took 0.4357600212097168s
Versatility | Serialization formats check for Publications Office Authority tables took 4.382591009140015s
Availability | RDF dump link check for Publications Office Authority tables took 0.22831034660339355s
License | MR license check for Publications Office Authority tables took 0.5157737731933594s
License | HR license check for Publications Office Authority tables took 300.10570907592773s
Amount of data | Number of property check for Publications Office Authority tables took 0.21606040000915527s
Understandability | Number of label check for Publications Office Authority tables took 1.8021838665008545s
Understandability | URI regex check for Publications Office Authority tables took 0.3921492099761963s
Understandability | Vocabs check for Publications Office Authority tables took 0.11167407035827637s
Verifiability | Authors check for Publications Office Authority tables took 0.250164270401001s
Verifiability | Publishers check for Publications Office Authority tables took 0.24500036239624023s
Performance | Throughput check for Publications Office Authority tables took 10.574944734573364s
Amount of data | Check the number of entities for Publications Office Authority tables took 7.05718994140625e-05s
Verifiability | Contribs. check for Publications Office Authority tables took 0.184478759765625s
Interlinking | sameAs chians check for Publications Office Authority tables took 7.512789726257324s
Interlinking | skos check for Publications Office Authority tables took 0.42316222190856934s
Interlinking | skos check for Publications Office Authority tables took 0.32594799995422363s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.359189510345459s
Currency | Creation date check for Publications Office Authority tables took 0.6323270797729492s
Currency | Modification date check for Publications Office Authority tables took 0.15517878532409668s
Rep.Conc. | URIs length for Publications Office Authority tables took 433.8919265270233s
Interoperability | New vocabularies check for Publications Office Authority tables took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.21135282516479492s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.21205401420593262s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.16034364700317383s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 42.47246336936951s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.2150957584381104s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.7197787761688232s
Consistency | Disjoint class check for Publications Office Authority tables took 0.17363476753234863s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.4392626285553s
Consistency | Misplaced classes for Publications Office Authority tables took 8.687497854232788s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 36.17582821846008s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.6305830478668213s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.6200668811798s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 3.095327377319336s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.4687838554382324s
Security | Sign check for Publications Office Authority tables took 0.264554500579834s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 11.311064720153809s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 26.685357093811035s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.022006511688232422s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 5.936622619628906e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 2.1457672119140625e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 9.5367431640625e-06s
INFO | --- Analysis for publications_office_authority_tables took 15061.44295334816s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 4.9114227294921875e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.31714534759521484s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.021520614624023438s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.4809112548828125e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 1.430511474609375e-05s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 80.17017936706543s
Availability | SPARQL endpoint availability check for QBOAirbase took 8.821487426757812e-05s
Availability | VoID file availability check for QBOAirbase took 0.0008957386016845703s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.32193470001220703s
Reputation | Calculation of the PageRank for QBOAirbase took 0.021668434143066406s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 9.1552734375e-05s
Believability | Calculation of trust value for QBOAirbase took 8.344650268554688e-06s
INFO | --- Analysis for qboairbase took 218.44916224479675s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 9.512901306152344e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 24.198685884475708s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.02231287956237793s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 3.4332275390625e-05s
Believability | Calculation of trust value for qualitywebdata.org took 1.3589859008789062e-05s
INFO | --- Analysis for qualitywebdata-org took 134.67464089393616s
Availability | SPARQL endpoint availability check for Qualité de l'air took 0.00010085105895996094s
Availability | VoID file availability check for Qualité de l'air took 0.0008671283721923828s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.34252357482910156s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.022458314895629883s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0009467601776123047s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 4.6253204345703125e-05s
Believability | Calculation of trust value for Qualité de l'air took 1.2636184692382812e-05s
INFO | --- Analysis for Qualité_de_l'air took 194.19228744506836s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 9.369850158691406e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0007457733154296875s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.4188497066497803s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.02190256118774414s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.9577484130859375e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 1.3113021850585938e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 348.64352583885193s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.6060841083526611s
Availability | VoID file availability check for Querolus in LiLa took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 23.87604284286499s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.021192550659179688s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 4.315376281738281e-05s
Believability | Calculation of trust value for Querolus in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for Querolus took 132.90951776504517s
Availability | SPARQL endpoint availability check for Quotations Book took 9.107589721679688e-05s
Availability | VoID file availability check for Quotations Book took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.31382322311401367s
Reputation | Calculation of the PageRank for Quotations Book took 0.021102428436279297s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.0008435249328613281s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 4.7206878662109375e-05s
Believability | Calculation of trust value for Quotations Book took 1.239776611328125e-05s
INFO | --- Analysis for quotations_book took 110.82258987426758s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.47308874130249023s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007052421569824219s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 29.199665546417236s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.7219870090484619s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.444643020629883s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.9119071960449219s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.622835874557495s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.550997018814087s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.19228434562683105s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1818697452545166s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13053131103515625s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14327788352966309s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.19103360176086426s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.19426512718200684s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1563735008239746s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2844421863555908s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15459108352661133s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14346742630004883s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14222145080566406s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.801526308059692s
Amount of data | Check the number of entities for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.200241088867188e-05s
Verifiability | Contribs. check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14241719245910645s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14206480979919434s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1541452407836914s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14277911186218262s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14799213409423828s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2969503402709961s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.37595677375793457s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 28.253734350204468s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14258074760437012s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14172768592834473s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1417698860168457s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14513897895812988s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.315376281738281e-05s
Accuracy | Check Datatype consistency for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.233450651168823s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1560206413269043s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.838709831237793s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.151770830154419s
Consistency | Check Invalid usage of undefined classes for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.486344575881958s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.061393737792969s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.8708040714263916s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13020896911621094s
Availability | Check URIs Dereferenciability for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 14.509198427200317s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2951502799987793s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.02391195297241211s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.555152893066406e-05s
Interoperability | Check the re-using of existing vocabs for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.1457672119140625e-06s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.9141387939453125e-06s
INFO | --- Analysis for racai-legalnero took 288.8696630001068s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 4.57763671875e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.29758787155151367s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.021178245544433594s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 4.696846008300781e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 1.239776611328125e-05s
INFO | --- Analysis for racai-llod-corola-we took 75.01829147338867s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.14430856704711914s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0006945133209228516s
Extra | Recovery of all triples for PARSEME-Ro corpus took 31.044536113739014s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.72859787940979s
Amount of data | Number of triples check for PARSEME-Ro corpus took 6.615675687789917s
Interoperability | New terms check for PARSEME-Ro corpus took 2.27571177482605s
Versatility | Languages check for PARSEME-Ro corpus took 17.83679962158203s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.36772346496582s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.13211870193481445s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.14412879943847656s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.14095330238342285s
License | MR license check for PARSEME-Ro corpus took 0.13094854354858398s
License | HR license check for PARSEME-Ro corpus took 10.142040967941284s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.14207816123962402s
Understandability | Number of label check for PARSEME-Ro corpus took 0.17641925811767578s
Understandability | URI regex check for PARSEME-Ro corpus took 0.260634183883667s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.14209747314453125s
Verifiability | Authors check for PARSEME-Ro corpus took 0.13148164749145508s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.13100981712341309s
Performance | Throughput check for PARSEME-Ro corpus took 10.77497148513794s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 9.298324584960938e-05s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.14188623428344727s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 0.14184904098510742s
Interlinking | skos check for PARSEME-Ro corpus took 0.14211773872375488s
Interlinking | skos check for PARSEME-Ro corpus took 0.14255523681640625s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 0.14215350151062012s
Currency | Creation date check for PARSEME-Ro corpus took 0.2849447727203369s
Currency | Modification date check for PARSEME-Ro corpus took 0.28456568717956543s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 79.98884797096252s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.15550756454467773s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.13009381294250488s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.13072538375854492s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 1.9620633125305176s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.23245954513549805s
Accuracy | Check Datatype consistency for PARSEME-Ro corpus took 4.109406232833862s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.13210654258728027s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 11.375965595245361s
Consistency | Check Ontology hijacking for PARSEME-Ro corpus took 31.678948402404785s
Consistency | Check Invalid usage of undefined classes for PARSEME-Ro corpus took 1.7253003120422363s
Consistency | Check Invalid usage of undefined properties for PARSEME-Ro corpus took 13.933097124099731s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 2.86468505859375s
Security | Sign check for PARSEME-Ro corpus took 0.14238786697387695s
Availability | Check URIs Dereferenciability for PARSEME-Ro corpus took 7.319405555725098s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.4105825424194336s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020826101303100586s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.7670135498046875e-05s
Interoperability | Check the re-using of existing vocabs for PARSEME-Ro corpus took 2.1457672119140625e-06s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.1920928955078125e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 325.76837372779846s
Availability | SPARQL endpoint availability check for RoLEX took 0.1566476821899414s
Availability | VoID file availability check for RoLEX took 0.0006046295166015625s
Extra | Recovery of all triples for RoLEX took 35.061333894729614s
Performance | Total latancy measurement for RoLEX took 0.7656474113464355s
Amount of data | Number of triples check for RoLEX took 1.5802605152130127s
Interoperability | New terms check for RoLEX took 1.8105823993682861s
Versatility | Languages check for RoLEX took 4.095383644104004s
Interpretability | Number of blank nodes check for RoLEX took 1.1647834777832031s
Interpretability | RDF structures check for RoLEX took 0.15460419654846191s
Versatility | Serialization formats check for RoLEX took 0.15350890159606934s
Availability | RDF dump link check for RoLEX took 0.1420285701751709s
License | MR license check for RoLEX took 0.15383148193359375s
License | HR license check for RoLEX took 0.14405465126037598s
Amount of data | Number of property check for RoLEX took 0.141845703125s
Understandability | Number of label check for RoLEX took 0.15533709526062012s
Understandability | URI regex check for RoLEX took 0.2743659019470215s
Understandability | Vocabs check for RoLEX took 0.13182830810546875s
Verifiability | Authors check for RoLEX took 0.1323084831237793s
Verifiability | Publishers check for RoLEX took 0.13155913352966309s
Performance | Throughput check for RoLEX took 10.389512300491333s
Amount of data | Check the number of entities for RoLEX took 6.127357482910156e-05s
Verifiability | Contribs. check for RoLEX took 0.1417529582977295s
Interlinking | sameAs chians check for RoLEX took 0.14174771308898926s
Interlinking | skos check for RoLEX took 0.14283537864685059s
Interlinking | skos check for RoLEX took 0.15372562408447266s
Timeliness | dataset update frequency check for RoLEX took 0.14279747009277344s
Currency | Creation date check for RoLEX took 0.2754170894622803s
Currency | Modification date check for RoLEX took 0.28701186180114746s
Rep.Conc. | URIs length for RoLEX took 58.67488765716553s
Interoperability | New vocabularies check for RoLEX took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for RoLEX took 0.14111042022705078s
Accuracy | Check Functional Property for RoLEX took 0.14014172554016113s
Accuracy | Check Inverse Functional Property for RoLEX took 0.15283679962158203s
Accuracy | Check Datatype consistency for RoLEX took 4.208188056945801s
Consistency | Disjoint class check for RoLEX took 0.14574217796325684s
Consistency | Check Misplaced properties for RoLEX took 2.6618926525115967s
Consistency | Check Ontology hijacking for RoLEX took 8.925740480422974s
Consistency | Check Invalid usage of undefined classes for RoLEX took 2.0326483249664307s
Consistency | Check Invalid usage of undefined properties for RoLEX took 4.005978107452393s
Conciseness | Check Extensional conciseness for RoLEX took 3.201197862625122s
Security | Sign check for RoLEX took 0.14117836952209473s
Availability | Check URIs Dereferenciability for RoLEX took 7.199967622756958s
Completeness | Calculation of interlinking completeness for RoLEX took 25.258341312408447s
Reputation | Calculation of the PageRank for RoLEX took 0.021079063415527344s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.790855407714844e-05s
Interoperability | Check the re-using of existing vocabs for RoLEX took 2.1457672119140625e-06s
Believability | Calculation of trust value for RoLEX took 1.239776611328125e-05s
INFO | --- Analysis for racai-llod-rolex took 225.64454007148743s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0003802776336669922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 23.237390756607056s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.023011207580566406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.600120544433594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 9.059906005859375e-06s
INFO | --- Analysis for racai-llod-romanian-treebank took 150.10010647773743s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.7206878662109375e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 26.20296812057495s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.022510528564453125s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 3.337860107421875e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 1.2636184692382812e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 154.79493403434753s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 9.846687316894531e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.33246946334838867s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.021548986434936523s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0009419918060302734s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 4.0531158447265625e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 1.1444091796875e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 27.605655670166016s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 0.00011134147644042969s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.00038313865661621094s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 27.711671113967896s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.021200180053710938s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 3.981590270996094e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.2636184692382812e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 180.4304642677307s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.13402795791625977s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0007760524749755859s
Extra | Recovery of all triples for ROBIN Technical Acquisition Speech Corpus took 9.648786544799805s
Performance | Total latancy measurement for ROBIN Technical Acquisition Speech Corpus took 0.7008395195007324s
Amount of data | Number of triples check for ROBIN Technical Acquisition Speech Corpus took 0.3040907382965088s
Interoperability | New terms check for ROBIN Technical Acquisition Speech Corpus took 1.5941381454467773s
Versatility | Languages check for ROBIN Technical Acquisition Speech Corpus took 0.6638338565826416s
Interpretability | Number of blank nodes check for ROBIN Technical Acquisition Speech Corpus took 0.25864243507385254s
Interpretability | RDF structures check for ROBIN Technical Acquisition Speech Corpus took 0.15398502349853516s
Versatility | Serialization formats check for ROBIN Technical Acquisition Speech Corpus took 0.1425614356994629s
Availability | RDF dump link check for ROBIN Technical Acquisition Speech Corpus took 0.15370774269104004s
License | MR license check for ROBIN Technical Acquisition Speech Corpus took 0.1408367156982422s
License | HR license check for ROBIN Technical Acquisition Speech Corpus took 0.1469106674194336s
Amount of data | Number of property check for ROBIN Technical Acquisition Speech Corpus took 0.13983368873596191s
Understandability | Number of label check for ROBIN Technical Acquisition Speech Corpus took 0.1455671787261963s
Understandability | URI regex check for ROBIN Technical Acquisition Speech Corpus took 0.2910304069519043s
Understandability | Vocabs check for ROBIN Technical Acquisition Speech Corpus took 0.13957786560058594s
Verifiability | Authors check for ROBIN Technical Acquisition Speech Corpus took 0.14143013954162598s
Verifiability | Publishers check for ROBIN Technical Acquisition Speech Corpus took 0.12920331954956055s
Performance | Throughput check for ROBIN Technical Acquisition Speech Corpus took 11.093421697616577s
Amount of data | Check the number of entities for ROBIN Technical Acquisition Speech Corpus took 7.343292236328125e-05s
Verifiability | Contribs. check for ROBIN Technical Acquisition Speech Corpus took 0.17183780670166016s
Interlinking | sameAs chians check for ROBIN Technical Acquisition Speech Corpus took 0.14165401458740234s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.1537020206451416s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.14194154739379883s
Timeliness | dataset update frequency check for ROBIN Technical Acquisition Speech Corpus took 0.15372157096862793s
Currency | Creation date check for ROBIN Technical Acquisition Speech Corpus took 0.2956864833831787s
Currency | Modification date check for ROBIN Technical Acquisition Speech Corpus took 0.2855641841888428s
Rep.Conc. | URIs length for ROBIN Technical Acquisition Speech Corpus took 2.6767776012420654s
Interoperability | New vocabularies check for ROBIN Technical Acquisition Speech Corpus took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for ROBIN Technical Acquisition Speech Corpus took 0.15291047096252441s
Accuracy | Check Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.15274763107299805s
Accuracy | Check Inverse Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.153519868850708s
Accuracy | Check Empty annotation labels for ROBIN Technical Acquisition Speech Corpus took 0.3969764709472656s
Accuracy | Check White space in annotation for ROBIN Technical Acquisition Speech Corpus took 0.0095977783203125s
Accuracy | Check Datatype consistency for ROBIN Technical Acquisition Speech Corpus took 1.268768548965454s
Consistency | Disjoint class check for ROBIN Technical Acquisition Speech Corpus took 0.13174033164978027s
Consistency | Check Misplaced properties for ROBIN Technical Acquisition Speech Corpus took 0.560697078704834s
Consistency | Check Ontology hijacking for ROBIN Technical Acquisition Speech Corpus took 2.1322543621063232s
Consistency | Check Invalid usage of undefined classes for ROBIN Technical Acquisition Speech Corpus took 1.3890225887298584s
Consistency | Check Invalid usage of undefined properties for ROBIN Technical Acquisition Speech Corpus took 1.7772047519683838s
Conciseness | Check Extensional conciseness for ROBIN Technical Acquisition Speech Corpus took 0.8516569137573242s
Security | Sign check for ROBIN Technical Acquisition Speech Corpus took 0.12818431854248047s
Availability | Check URIs Dereferenciability for ROBIN Technical Acquisition Speech Corpus took 3611.066716194153s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 27.160084009170532s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.022287607192993164s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 6.008148193359375e-05s
Interoperability | Check the re-using of existing vocabs for ROBIN Technical Acquisition Speech Corpus took 1.6689300537109375e-06s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 1.2636184692382812e-05s
INFO | --- Analysis for racai-llod-rtasc took 3763.509540081024s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.21721529960632324s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.000682830810546875s
Extra | Recovery of all triples for SiMoNERo - the Romanian medical treebank took 34.412904262542725s
Performance | Total latancy measurement for SiMoNERo - the Romanian medical treebank took 0.73575758934021s
Amount of data | Number of triples check for SiMoNERo - the Romanian medical treebank took 1.0462532043457031s
Interoperability | New terms check for SiMoNERo - the Romanian medical treebank took 1.5936155319213867s
Versatility | Languages check for SiMoNERo - the Romanian medical treebank took 2.507497787475586s
Interpretability | Number of blank nodes check for SiMoNERo - the Romanian medical treebank took 0.8516654968261719s
Interpretability | RDF structures check for SiMoNERo - the Romanian medical treebank took 0.14390945434570312s
Versatility | Serialization formats check for SiMoNERo - the Romanian medical treebank took 0.14298677444458008s
Availability | RDF dump link check for SiMoNERo - the Romanian medical treebank took 0.14173102378845215s
License | MR license check for SiMoNERo - the Romanian medical treebank took 0.14301562309265137s
License | HR license check for SiMoNERo - the Romanian medical treebank took 4.7878577709198s
Amount of data | Number of property check for SiMoNERo - the Romanian medical treebank took 0.16179418563842773s
Understandability | Number of label check for SiMoNERo - the Romanian medical treebank took 0.14812731742858887s
Understandability | URI regex check for SiMoNERo - the Romanian medical treebank took 0.2951028347015381s
Understandability | Vocabs check for SiMoNERo - the Romanian medical treebank took 0.1456584930419922s
Verifiability | Authors check for SiMoNERo - the Romanian medical treebank took 0.13164424896240234s
Verifiability | Publishers check for SiMoNERo - the Romanian medical treebank took 0.14267945289611816s
Performance | Throughput check for SiMoNERo - the Romanian medical treebank took 10.86365795135498s
Amount of data | Check the number of entities for SiMoNERo - the Romanian medical treebank took 0.00011157989501953125s
Verifiability | Contribs. check for SiMoNERo - the Romanian medical treebank took 0.15417122840881348s
Interlinking | sameAs chians check for SiMoNERo - the Romanian medical treebank took 0.14121413230895996s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.13545608520507812s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.13037705421447754s
Timeliness | dataset update frequency check for SiMoNERo - the Romanian medical treebank took 0.14182615280151367s
Currency | Creation date check for SiMoNERo - the Romanian medical treebank took 0.2845625877380371s
Currency | Modification date check for SiMoNERo - the Romanian medical treebank took 0.28171205520629883s
Rep.Conc. | URIs length for SiMoNERo - the Romanian medical treebank took 9.532730102539062s
Interoperability | New vocabularies check for SiMoNERo - the Romanian medical treebank took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for SiMoNERo - the Romanian medical treebank took 0.14104175567626953s
Accuracy | Check Functional Property for SiMoNERo - the Romanian medical treebank took 0.15097332000732422s
Accuracy | Check Inverse Functional Property for SiMoNERo - the Romanian medical treebank took 0.1279895305633545s
Accuracy | Check Empty annotation labels for SiMoNERo - the Romanian medical treebank took 0.7401628494262695s
Accuracy | Check White space in annotation for SiMoNERo - the Romanian medical treebank took 0.0194547176361084s
Accuracy | Check Datatype consistency for SiMoNERo - the Romanian medical treebank took 4.162569522857666s
Consistency | Disjoint class check for SiMoNERo - the Romanian medical treebank took 0.14510059356689453s
Consistency | Check Misplaced properties for SiMoNERo - the Romanian medical treebank took 1.7502129077911377s
Consistency | Check Ontology hijacking for SiMoNERo - the Romanian medical treebank took 4.709741115570068s
Consistency | Check Invalid usage of undefined classes for SiMoNERo - the Romanian medical treebank took 1.4262616634368896s
Consistency | Check Invalid usage of undefined properties for SiMoNERo - the Romanian medical treebank took 2.95289945602417s
Conciseness | Check Extensional conciseness for SiMoNERo - the Romanian medical treebank took 2.990795373916626s
Security | Sign check for SiMoNERo - the Romanian medical treebank took 0.1425466537475586s
Availability | Check URIs Dereferenciability for SiMoNERo - the Romanian medical treebank took 74867.91319704056s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 60.02791976928711s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.022017717361450195s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 5.7220458984375e-05s
Interoperability | Check the re-using of existing vocabs for SiMoNERo - the Romanian medical treebank took 1.1920928955078125e-06s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 1.5735626220703125e-05s
INFO | --- Analysis for racai-llod-simonero took 75690.01867771149s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.0001049041748046875s
Availability | VoID file availability check for Rådata nå! took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Rådata nå! took 60.01889228820801s
Reputation | Calculation of the PageRank for Rådata nå! took 0.02152395248413086s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 9.965896606445312e-05s
Believability | Calculation of trust value for Rådata nå! took 1.52587890625e-05s
INFO | --- Analysis for radatana took 600.2964811325073s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 8.7738037109375e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0007233619689941406s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 60.02721452713013s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.027439355850219727s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 5.173683166503906e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 1.049041748046875e-05s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 600.2967813014984s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 0.00011897087097167969s
Availability | VoID file availability check for Raphael Research Resource took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 60.02563428878784s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.0213320255279541s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 4.887580871582031e-05s
Believability | Calculation of trust value for Raphael Research Resource took 1.430511474609375e-05s
INFO | --- Analysis for raphaelresearchresource took 600.3075420856476s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 0.000141143798828125s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0007288455963134766s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 60.02422261238098s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.021572351455688477s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 4.410743713378906e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.5020370483398438e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 600.2920625209808s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 4.649162292480469e-05s
Availability | VoID file availability check for Polish LGU financial statements took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 60.02674961090088s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.021602392196655273s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 4.172325134277344e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 1.4543533325195312e-05s
INFO | --- Analysis for Rb_PL_LGU took 600.301557302475s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 0.00010228157043457031s
Availability | VoID file availability check for RDF Book Mashup took 0.0006797313690185547s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 60.02417993545532s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.021823883056640625s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 0.0001068115234375s
Believability | Calculation of trust value for RDF Book Mashup took 1.3828277587890625e-05s
INFO | --- Analysis for rdf-book-mashup took 600.3068478107452s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 0.00013518333435058594s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0007658004760742188s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 60.02269148826599s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.021332740783691406s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00011444091796875s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 9.775161743164062e-06s
INFO | --- Analysis for rdfize-lastfm took 600.2843129634857s
Availability | SPARQL endpoint availability check for RDFLicense took 9.202957153320312e-05s
Availability | VoID file availability check for RDFLicense took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for RDFLicense took 60.02820873260498s
Reputation | Calculation of the PageRank for RDFLicense took 0.021847963333129883s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 4.458427429199219e-05s
Believability | Calculation of trust value for RDFLicense took 1.4066696166992188e-05s
INFO | --- Analysis for rdflicense took 600.2968220710754s
Availability | SPARQL endpoint availability check for RDFohloh took 9.560585021972656e-05s
Availability | VoID file availability check for RDFohloh took 0.0007159709930419922s
Completeness | Calculation of interlinking completeness for RDFohloh took 60.029175758361816s
Reputation | Calculation of the PageRank for RDFohloh took 0.02190375328063965s
Interlinking | Calculation of Degree of Connection for RDFohloh took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 0.00011229515075683594s
Believability | Calculation of trust value for RDFohloh took 1.049041748046875e-05s
INFO | --- Analysis for rdfohloh took 600.298047542572s
Availability | SPARQL endpoint availability check for Reactome RDF took 9.918212890625e-05s
Availability | VoID file availability check for Reactome RDF took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for Reactome RDF took 60.02700662612915s
Reputation | Calculation of the PageRank for Reactome RDF took 0.02163553237915039s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 5.221366882324219e-05s
Believability | Calculation of trust value for Reactome RDF took 1.5020370483398438e-05s
INFO | --- Analysis for reactome-rdf took 600.2948179244995s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.00011134147644042969s
Availability | VoID file availability check for Rechtspraak.nl took 0.0007519721984863281s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 60.02259373664856s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.02156972885131836s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 0.00010538101196289062s
Believability | Calculation of trust value for Rechtspraak.nl took 1.5020370483398438e-05s
INFO | --- Analysis for rechtspraak took 600.2890019416809s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 9.059906005859375e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 60.02935290336609s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.02115464210510254s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 0.0001049041748046875s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 2.1457672119140625e-05s
INFO | --- Analysis for red-uno-internacional-santillana took 600.303717136383s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.00010061264038085938s
Availability | VoID file availability check for reference.data.gov.uk took 0.0008199214935302734s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 60.02606010437012s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.0219423770904541s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00017523765563964844s
Believability | Calculation of trust value for reference.data.gov.uk took 1.4781951904296875e-05s
INFO | --- Analysis for reference-data-gov-uk took 600.3051478862762s
Availability | SPARQL endpoint availability check for Regiony took 9.202957153320312e-05s
Availability | VoID file availability check for Regiony took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for Regiony took 60.02774167060852s
Reputation | Calculation of the PageRank for Regiony took 0.021256685256958008s
Interlinking | Calculation of Degree of Connection for Regiony took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Regiony took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Regiony took 4.5299530029296875e-05s
Believability | Calculation of trust value for Regiony took 1.5735626220703125e-05s
INFO | --- Analysis for regiony took 600.3022925853729s
Availability | SPARQL endpoint availability check for RELD took 9.393692016601562e-05s
Availability | VoID file availability check for RELD took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for RELD took 60.025054931640625s
Reputation | Calculation of the PageRank for RELD took 0.021382808685302734s
Interlinking | Calculation of Degree of Connection for RELD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for RELD took 4.076957702636719e-05s
Believability | Calculation of trust value for RELD took 1.4781951904296875e-05s
INFO | --- Analysis for RELD took 600.3015213012695s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.00010061264038085938s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0007319450378417969s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 60.024821519851685s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.021238327026367188s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 5.0067901611328125e-05s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 1.430511474609375e-05s
INFO | --- Analysis for reload took 600.2853543758392s
Availability | SPARQL endpoint availability check for Land use merced dataset took 9.894371032714844e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 60.02725625038147s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.021468162536621094s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 4.982948303222656e-05s
Believability | Calculation of trust value for Land use merced dataset took 1.3589859008789062e-05s
INFO | --- Analysis for remote_Sensing took 600.2922186851501s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 0.00015020370483398438s
Availability | VoID file availability check for Renewable Energy Generators took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 60.02918076515198s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.021364212036132812s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 5.459785461425781e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 8.58306884765625e-06s
INFO | --- Analysis for renewable_energy_generators took 600.3128554821014s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.00010561943054199219s
Availability | VoID file availability check for research.data.gov.uk took 0.0004127025604248047s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 60.02382445335388s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.021445274353027344s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 0.00011277198791503906s
Believability | Calculation of trust value for research.data.gov.uk took 1.8596649169921875e-05s
INFO | --- Analysis for research-data-gov-uk took 600.2702469825745s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 9.369850158691406e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 60.026965618133545s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.02194976806640625s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 4.863739013671875e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 1.4066696166992188e-05s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 600.2975389957428s
Availability | SPARQL endpoint availability check for Restaurantes took 9.107589721679688e-05s
Availability | VoID file availability check for Restaurantes took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for Restaurantes took 60.02710700035095s
Reputation | Calculation of the PageRank for Restaurantes took 0.02436208724975586s
Interlinking | Calculation of Degree of Connection for Restaurantes took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Restaurantes took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 5.245208740234375e-05s
Believability | Calculation of trust value for Restaurantes took 1.3828277587890625e-05s
INFO | --- Analysis for restaurantes-zaragoza took 600.3136458396912s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 9.107589721679688e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.00072479248046875s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 60.02114415168762s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.021419048309326172s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 8.7738037109375e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 1.2874603271484375e-05s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 600.2957878112793s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 9.632110595703125e-05s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 60.028846979141235s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.02135753631591797s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 4.2438507080078125e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 1.4781951904296875e-05s
INFO | --- Analysis for revistas_turismo took 600.2985711097717s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.00010323524475097656s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0007152557373046875s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 60.0250084400177s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.02138543128967285s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00012612342834472656s
Believability | Calculation of trust value for Revyu.com - Review Anything took 1.4781951904296875e-05s
INFO | --- Analysis for revyu took 600.2978863716125s
Availability | SPARQL endpoint availability check for sdafsadf took 0.0001068115234375s
Availability | VoID file availability check for sdafsadf took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for sdafsadf took 60.02416777610779s
Reputation | Calculation of the PageRank for sdafsadf took 0.021213531494140625s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 4.553794860839844e-05s
Believability | Calculation of trust value for sdafsadf took 1.9550323486328125e-05s
INFO | --- Analysis for rgsdfg took 600.2761044502258s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.00012731552124023438s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 60.02893328666687s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.021379709243774414s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 5.793571472167969e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 1.52587890625e-05s
INFO | --- Analysis for riese took 600.3017840385437s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 9.012222290039062e-05s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 60.0279757976532s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.021135807037353516s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 5.364418029785156e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 9.059906005859375e-06s
INFO | --- Analysis for rism took 600.2838113307953s
Availability | SPARQL endpoint availability check for RISM Authority data took 9.822845458984375e-05s
Availability | VoID file availability check for RISM Authority data took 0.0007600784301757812s
Completeness | Calculation of interlinking completeness for RISM Authority data took 60.027926445007324s
Reputation | Calculation of the PageRank for RISM Authority data took 0.02221965789794922s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 5.602836608886719e-05s
Believability | Calculation of trust value for RISM Authority data took 1.4066696166992188e-05s
INFO | --- Analysis for rism-authorities took 600.2966063022614s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 0.00010156631469726562s
Availability | VoID file availability check for engineering equipment ontology took 0.0007369518280029297s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 60.0266752243042s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.021407365798950195s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 4.076957702636719e-05s
Believability | Calculation of trust value for engineering equipment ontology took 9.5367431640625e-06s
INFO | --- Analysis for rk took 600.2910265922546s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00010943412780761719s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007374286651611328s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 60.02265429496765s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.022645235061645508s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00024247169494628906s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 1.5497207641601562e-05s
INFO | --- Analysis for rkb-explorer-acm took 600.2927148342133s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 9.965896606445312e-05s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 60.022807598114014s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.02143096923828125s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00015497207641601562s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-budapest took 600.2857303619385s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.00012135505676269531s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 60.024632930755615s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.021252155303955078s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00021600723266601562s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-citeseer took 600.3036510944366s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 9.083747863769531e-05s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 60.02713704109192s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.027266502380371094s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00017547607421875s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-cordis took 600.3061654567719s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.00011324882507324219s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 60.02553963661194s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.022639036178588867s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0009043216705322266s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.0002143383026123047s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-courseware took 600.2863118648529s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.00010037422180175781s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0007002353668212891s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 60.026949882507324s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.021183013916015625s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 5.555152893066406e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-crime took 600.3109269142151s
Availability | SPARQL endpoint availability check for crm took 0.00010037422180175781s
Availability | VoID file availability check for crm took 0.0007007122039794922s
Completeness | Calculation of interlinking completeness for crm took 60.02576756477356s
Reputation | Calculation of the PageRank for crm took 0.021497011184692383s
Interlinking | Calculation of Degree of Connection for crm took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for crm took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for crm took 3.314018249511719e-05s
Believability | Calculation of trust value for crm took 1.5735626220703125e-05s
INFO | --- Analysis for rkb-explorer-crm took 600.2881367206573s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00010156631469726562s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0004184246063232422s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 60.023539304733276s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.021905899047851562s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00014090538024902344s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.5020370483398438e-05s
INFO | --- Analysis for rkb-explorer-curriculum took 600.3011929988861s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.00010752677917480469s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 60.02599596977234s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.02165079116821289s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0008184909820556641s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 7.200241088867188e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 600.296425819397s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 8.916854858398438e-05s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0008492469787597656s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 60.03002119064331s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.02230668067932129s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.00027298927307128906s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-dblp took 600.3014950752258s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.00010323524475097656s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 60.02449059486389s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.021466970443725586s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 8.678436279296875e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-deepblue took 600.3005068302155s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.00010156631469726562s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 60.027907609939575s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.022435426712036133s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 0.00010967254638671875s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-deploy took 600.3085701465607s
Availability | SPARQL endpoint availability check for digitaleconomy took 9.083747863769531e-05s
Availability | VoID file availability check for digitaleconomy took 0.0007572174072265625s
Completeness | Calculation of interlinking completeness for digitaleconomy took 60.02566385269165s
Reputation | Calculation of the PageRank for digitaleconomy took 0.02119922637939453s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 4.553794860839844e-05s
Believability | Calculation of trust value for digitaleconomy took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 600.3040640354156s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.00010156631469726562s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 60.026850938797s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.021544456481933594s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00015783309936523438s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-dotac took 600.2963349819183s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 9.846687316894531e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 60.02813100814819s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.027270793914794922s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.6743621826171875e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-ecs took 600.2941696643829s
Availability | SPARQL endpoint availability check for enaktingpsi took 9.5367431640625e-05s
Availability | VoID file availability check for enaktingpsi took 0.0007085800170898438s
Completeness | Calculation of interlinking completeness for enaktingpsi took 60.0289032459259s
Reputation | Calculation of the PageRank for enaktingpsi took 0.025203704833984375s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0008146762847900391s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 4.744529724121094e-05s
Believability | Calculation of trust value for enaktingpsi took 1.52587890625e-05s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 600.2975878715515s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 9.870529174804688e-05s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 60.02461218833923s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.021775007247924805s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0008091926574707031s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00019812583923339844s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-eprints took 600.297976732254s
Availability | SPARQL endpoint availability check for epsrc took 0.00010013580322265625s
Availability | VoID file availability check for epsrc took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for epsrc took 60.029746294021606s
Reputation | Calculation of the PageRank for epsrc took 0.021419048309326172s
Interlinking | Calculation of Degree of Connection for epsrc took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for epsrc took 6.437301635742188e-05s
Believability | Calculation of trust value for epsrc took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-epsrc took 600.2884211540222s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.00011301040649414062s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 60.0283305644989s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.021288156509399414s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 9.989738464355469e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-era took 600.3663218021393s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.00010824203491210938s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 60.02726435661316s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.021240711212158203s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.000118255615234375s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-eurecom took 600.3094606399536s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 0.00011515617370605469s
Availability | VoID file availability check for rkb-explorer-foreign took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 60.02898859977722s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.022880077362060547s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 5.1975250244140625e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-foreign took 600.2967956066132s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.00010275840759277344s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 60.02818298339844s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.026338815689086914s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 7.43865966796875e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.001483917236328125s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 0.00016355514526367188s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 1.52587890625e-05s
INFO | --- Analysis for rkb-explorer-ft took 600.3001027107239s
Availability | SPARQL endpoint availability check for fun took 0.00011134147644042969s
Availability | VoID file availability check for fun took 0.0007348060607910156s
Completeness | Calculation of interlinking completeness for fun took 60.02981114387512s
Reputation | Calculation of the PageRank for fun took 0.021144628524780273s
Interlinking | Calculation of Degree of Connection for fun took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for fun took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for fun took 9.703636169433594e-05s
Believability | Calculation of trust value for fun took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-fun took 600.3034064769745s
Availability | SPARQL endpoint availability check for gdlc took 4.6253204345703125e-05s
Availability | VoID file availability check for gdlc took 0.0007352828979492188s
Completeness | Calculation of interlinking completeness for gdlc took 60.025330543518066s
Reputation | Calculation of the PageRank for gdlc took 0.021574020385742188s
Interlinking | Calculation of Degree of Connection for gdlc took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for gdlc took 8.058547973632812e-05s
Believability | Calculation of trust value for gdlc took 1.5020370483398438e-05s
INFO | --- Analysis for rkb-explorer-gdlc took 600.2695453166962s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 9.036064147949219e-05s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 60.02623629570007s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.02150726318359375s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.0001361370086669922s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-ibm took 600.2876079082489s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.00010037422180175781s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 60.025540828704834s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.021434545516967773s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.00015735626220703125s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 2.0742416381835938e-05s
INFO | --- Analysis for rkb-explorer-ieee took 600.2933988571167s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 9.489059448242188e-05s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 60.02690052986145s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.021185636520385742s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.000148773193359375s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.7881393432617188e-05s
INFO | --- Analysis for rkb-explorer-irit took 600.2989292144775s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 9.72747802734375e-05s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007493495941162109s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 60.02693748474121s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.023918867111206055s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007948875427246094s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 7.963180541992188e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-italy took 600.3037061691284s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.00010776519775390625s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 60.02747893333435s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.021842241287231445s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 8.893013000488281e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 3.170967102050781e-05s
INFO | --- Analysis for rkb-explorer-jisc took 600.3126122951508s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 5.1021575927734375e-05s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 60.027852296829224s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.02163100242614746s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0008091926574707031s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 5.9604644775390625e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-kaunas took 600.3039395809174s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 9.298324584960938e-05s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 60.0251522064209s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.02198195457458496s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00017499923706054688s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 1.5497207641601562e-05s
INFO | --- Analysis for rkb-explorer-kisti took 600.2968304157257s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 9.417533874511719e-05s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 60.02365851402283s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.021778345108032227s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.0001666545867919922s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-laas took 600.2808327674866s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 5.1975250244140625e-05s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 60.0277533531189s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.021609067916870117s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 8.559226989746094e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.5497207641601562e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 600.2874817848206s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0001010894775390625s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 60.02923274040222s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.021070241928100586s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.0001804828643798828s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 600.276614189148s
Availability | SPARQL endpoint availability check for notube took 5.555152893066406e-05s
Availability | VoID file availability check for notube took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for notube took 60.02726745605469s
Reputation | Calculation of the PageRank for notube took 0.021540164947509766s
Interlinking | Calculation of Degree of Connection for notube took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for notube took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for notube took 6.175041198730469e-05s
Believability | Calculation of trust value for notube took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-notube took 600.2838895320892s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 9.870529174804688e-05s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0006899833679199219s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 60.02706027030945s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.02132105827331543s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00015282630920410156s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-nsf took 600.2922766208649s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00010323524475097656s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 60.02682614326477s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.021274566650390625s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0001773834228515625s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.621246337890625e-05s
INFO | --- Analysis for rkb-explorer-oai took 600.2787878513336s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 0.00011491775512695312s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.0007789134979248047s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 60.029847860336304s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.0211794376373291s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 4.220008850097656e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-opencyc took 600.2940180301666s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.00010085105895996094s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 60.02638840675354s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.0218045711517334s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 8.988380432128906e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.5020370483398438e-05s
INFO | --- Analysis for rkb-explorer-os took 600.3050906658173s
Availability | SPARQL endpoint availability check for photos took 0.00011277198791503906s
Availability | VoID file availability check for photos took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for photos took 60.02635478973389s
Reputation | Calculation of the PageRank for photos took 0.02167034149169922s
Interlinking | Calculation of Degree of Connection for photos took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for photos took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for photos took 9.107589721679688e-05s
Believability | Calculation of trust value for photos took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-photos took 600.2857213020325s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.00010228157043457031s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 60.02956175804138s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.021638870239257812s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00013065338134765625s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 2.2411346435546875e-05s
INFO | --- Analysis for rkb-explorer-pisa took 600.3179824352264s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0001456737518310547s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007503032684326172s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 60.02510952949524s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.021181583404541016s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.0002186298370361328s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-rae2001 took 600.3165347576141s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 9.775161743164062e-05s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0006928443908691406s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 60.027183294296265s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.021988391876220703s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00016641616821289062s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.5974044799804688e-05s
INFO | --- Analysis for rkb-explorer-resex took 600.2907464504242s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.00010275840759277344s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 60.02458834648132s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.0212857723236084s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 0.00010728836059570312s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-risks took 600.3129181861877s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00010156631469726562s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 60.02635478973389s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.02136969566345215s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00014209747314453125s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.6927719116210938e-05s
INFO | --- Analysis for rkb-explorer-roma took 600.2996697425842s
Availability | SPARQL endpoint availability check for roni took 0.00010919570922851562s
Availability | VoID file availability check for roni took 0.0006799697875976562s
Completeness | Calculation of interlinking completeness for roni took 60.02832841873169s
Reputation | Calculation of the PageRank for roni took 0.024184703826904297s
Interlinking | Calculation of Degree of Connection for roni took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for roni took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for roni took 3.719329833984375e-05s
Believability | Calculation of trust value for roni took 1.5020370483398438e-05s
INFO | --- Analysis for rkb-explorer-roni took 600.2891750335693s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00010037422180175781s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0006868839263916016s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 60.02392554283142s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0211336612701416s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0002269744873046875s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-southampton took 600.2962689399719s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 9.989738464355469e-05s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 60.01971626281738s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.021527528762817383s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00012135505676269531s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-ulm took 600.2961149215698s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.00010204315185546875s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 60.02828598022461s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.021839141845703125s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 3.2901763916015625e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0011594295501708984s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 0.00014209747314453125s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-unlocode took 600.291595697403s
Availability | SPARQL endpoint availability check for webconf took 5.245208740234375e-05s
Availability | VoID file availability check for webconf took 0.0004153251647949219s
Completeness | Calculation of interlinking completeness for webconf took 60.02559185028076s
Reputation | Calculation of the PageRank for webconf took 0.023149490356445312s
Interlinking | Calculation of Degree of Connection for webconf took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for webconf took 0.0008974075317382812s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00012826919555664062s
Believability | Calculation of trust value for webconf took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-webconf took 600.2830390930176s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.0001049041748046875s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 60.02476739883423s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.021388530731201172s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 8.416175842285156e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-webscience took 600.3044891357422s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.00010657310485839844s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 60.03002119064331s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.022500276565551758s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.0002224445343017578s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 1.5020370483398438e-05s
INFO | --- Analysis for rkb-explorer-wiki took 600.3022480010986s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.00010728836059570312s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 60.02794790267944s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.021239280700683594s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 0.0001125335693359375s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-wordnet took 600.2949185371399s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 0.00010395050048828125s
Availability | VoID file availability check for RKB Explorer Data took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 60.02463126182556s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.02215862274169922s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 4.0531158447265625e-05s
Believability | Calculation of trust value for RKB Explorer Data took 1.621246337890625e-05s
INFO | --- Analysis for rkb_explorer_data took 600.2803077697754s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 9.298324584960938e-05s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 60.02849745750427s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.02133798599243164s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 9.512901306152344e-05s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 1.430511474609375e-05s
INFO | --- Analysis for roceeh-road took 620.3153693675995s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 0.00010347366333007812s
Availability | VoID file availability check for ontology terrorist attack took 0.0007343292236328125s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 60.02558922767639s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.02119898796081543s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 3.5762786865234375e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 4.553794860839844e-05s
Believability | Calculation of trust value for ontology terrorist attack took 1.5735626220703125e-05s
INFO | --- Analysis for ROSHANI took 600.304342508316s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 0.00013208389282226562s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 60.01980638504028s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.02138495445251465s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 4.6253204345703125e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 1.4066696166992188e-05s
INFO | --- Analysis for ROSHANI_SAHU took 600.2844774723053s
Availability | SPARQL endpoint availability check for x took 0.00011324882507324219s
Availability | VoID file availability check for x took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for x took 60.03181290626526s
Reputation | Calculation of the PageRank for x took 0.021431922912597656s
Interlinking | Calculation of Degree of Connection for x took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for x took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for x took 5.030632019042969e-05s
Believability | Calculation of trust value for x took 2.1696090698242188e-05s
INFO | --- Analysis for Rozprawa,_artykuł took 600.2887299060822s
Availability | SPARQL endpoint availability check for Rpm Find took 4.7206878662109375e-05s
Availability | VoID file availability check for Rpm Find took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Rpm Find took 60.024428606033325s
Reputation | Calculation of the PageRank for Rpm Find took 0.021672964096069336s
Interlinking | Calculation of Degree of Connection for Rpm Find took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Rpm Find took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 4.7206878662109375e-05s
Believability | Calculation of trust value for Rpm Find took 1.4781951904296875e-05s
INFO | --- Analysis for rpm_find took 600.2909860610962s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 5.054473876953125e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 60.02771544456482s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.023293018341064453s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 8.392333984375e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 1.4543533325195312e-05s
INFO | --- Analysis for rss-500-nif-ner-corpus took 600.3114244937897s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 9.226799011230469e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 60.025506258010864s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.021341562271118164s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 8.392333984375e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 1.52587890625e-05s
INFO | --- Analysis for rubentaelman took 600.3037803173065s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 9.274482727050781e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 60.02994680404663s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.021137475967407227s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 9.322166442871094e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 1.5735626220703125e-05s
INFO | --- Analysis for rubenverborgh took 600.2811472415924s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 5.7220458984375e-05s
Availability | VoID file availability check for Russian Universities Specialities took 0.001589059829711914s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 60.02677273750305s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.021899938583374023s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.982948303222656e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 1.2874603271484375e-05s
INFO | --- Analysis for russian-universities-specialities took 600.301456451416s
Availability | SPARQL endpoint availability check for RxNorm took 9.942054748535156e-05s
Availability | VoID file availability check for RxNorm took 0.0008127689361572266s
Completeness | Calculation of interlinking completeness for RxNorm took 60.0275502204895s
Reputation | Calculation of the PageRank for RxNorm took 0.021543264389038086s
Interlinking | Calculation of Degree of Connection for RxNorm took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RxNorm took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for RxNorm took 5.3882598876953125e-05s
Believability | Calculation of trust value for RxNorm took 1.4543533325195312e-05s
INFO | --- Analysis for rxnorm took 600.2979938983917s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 5.626678466796875e-05s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0007233619689941406s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 60.025516986846924s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.021291255950927734s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 4.7206878662109375e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 1.430511474609375e-05s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 600.2971475124359s
Availability | SPARQL endpoint availability check for SALDO-RDF took 9.1552734375e-05s
Availability | VoID file availability check for SALDO-RDF took 0.0007803440093994141s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 60.0230188369751s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.021571874618530273s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007998943328857422s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 6.175041198730469e-05s
Believability | Calculation of trust value for SALDO-RDF took 1.4066696166992188e-05s
INFO | --- Analysis for saldo-rdf took 600.2915642261505s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 9.059906005859375e-05s
Availability | VoID file availability check for SALDOM-RDF took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 60.02450251579285s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.021422624588012695s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 4.9114227294921875e-05s
Believability | Calculation of trust value for SALDOM-RDF took 9.775161743164062e-06s
INFO | --- Analysis for saldom-rdf took 600.2964642047882s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 0.00011849403381347656s
Availability | VoID file availability check for Salzburgerland DE took 0.0008127689361572266s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 60.02811074256897s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.02132439613342285s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00018477439880371094s
Believability | Calculation of trust value for Salzburgerland DE took 1.5020370483398438e-05s
INFO | --- Analysis for salzburgerland-com-de took 600.298755645752s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 0.00010347366333007812s
Availability | VoID file availability check for Salzburgerland EN took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 60.025739431381226s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.021474599838256836s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00011515617370605469s
Believability | Calculation of trust value for Salzburgerland EN took 1.2636184692382812e-05s
INFO | --- Analysis for salzburgerland-com-en took 600.2832412719727s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 9.250640869140625e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0007677078247070312s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 60.026703119277954s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.021395206451416016s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00012803077697753906s
Believability | Calculation of trust value for Salzburgerland IT took 1.4066696166992188e-05s
INFO | --- Analysis for salzburgerland-com-it took 600.291100025177s
Availability | SPARQL endpoint availability check for sameAs.org took 9.298324584960938e-05s
Availability | VoID file availability check for sameAs.org took 0.0007700920104980469s
Completeness | Calculation of interlinking completeness for sameAs.org took 60.02769422531128s
Reputation | Calculation of the PageRank for sameAs.org took 0.02194952964782715s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0008323192596435547s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 4.553794860839844e-05s
Believability | Calculation of trust value for sameAs.org took 1.621246337890625e-05s
INFO | --- Analysis for sameas-org took 600.2976491451263s
Availability | SPARQL endpoint availability check for sandrart.net took 9.775161743164062e-05s
Availability | VoID file availability check for sandrart.net took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for sandrart.net took 60.021716833114624s
Reputation | Calculation of the PageRank for sandrart.net took 0.023751258850097656s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 7.653236389160156e-05s
Believability | Calculation of trust value for sandrart.net took 9.298324584960938e-06s
INFO | --- Analysis for sandrart-net took 600.3058693408966s
Availability | SPARQL endpoint availability check for Taxons  took 4.8160552978515625e-05s
Availability | VoID file availability check for Taxons  took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for Taxons  took 60.02286386489868s
Reputation | Calculation of the PageRank for Taxons  took 0.02601003646850586s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Taxons  took 8.368492126464844e-05s
Believability | Calculation of trust value for Taxons  took 1.0967254638671875e-05s
INFO | --- Analysis for sandre took 600.2940459251404s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 0.00010156631469726562s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 60.02424073219299s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.02146601676940918s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 4.935264587402344e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 1.4066696166992188e-05s
INFO | --- Analysis for sanskrit-english-lexicon took 600.2887344360352s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 0.00010800361633300781s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0008001327514648438s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 60.02583694458008s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.021497249603271484s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 5.316734313964844e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 1.5497207641601562e-05s
INFO | --- Analysis for santillana_guide_dataset took 600.3025569915771s
Availability | SPARQL endpoint availability check for SATAR test  took 0.00010275840759277344s
Availability | VoID file availability check for SATAR test  took 0.0008265972137451172s
Completeness | Calculation of interlinking completeness for SATAR test  took 60.029046058654785s
Reputation | Calculation of the PageRank for SATAR test  took 0.022011280059814453s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 4.315376281738281e-05s
Believability | Calculation of trust value for SATAR test  took 1.5020370483398438e-05s
INFO | --- Analysis for SATAR_test took 600.297954082489s
Availability | SPARQL endpoint availability check for SCBG Data took 6.532669067382812e-05s
Availability | VoID file availability check for SCBG Data took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for SCBG Data took 60.02441334724426s
Reputation | Calculation of the PageRank for SCBG Data took 0.021378040313720703s
Interlinking | Calculation of Degree of Connection for SCBG Data took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0008292198181152344s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 0.00010037422180175781s
Believability | Calculation of trust value for SCBG Data took 1.0251998901367188e-05s
INFO | --- Analysis for SCBG-Data took 600.2932448387146s
Availability | SPARQL endpoint availability check for schema.org took 0.00010323524475097656s
Availability | VoID file availability check for schema.org took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for schema.org took 60.02791094779968s
Reputation | Calculation of the PageRank for schema.org took 0.021241188049316406s
Interlinking | Calculation of Degree of Connection for schema.org took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for schema.org took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for schema.org took 5.269050598144531e-05s
Believability | Calculation of trust value for schema.org took 1.430511474609375e-05s
INFO | --- Analysis for schema-org took 600.2979528903961s
Availability | SPARQL endpoint availability check for Schemantra took 9.584426879882812e-05s
Availability | VoID file availability check for Schemantra took 0.0007243156433105469s
Completeness | Calculation of interlinking completeness for Schemantra took 60.026193618774414s
Reputation | Calculation of the PageRank for Schemantra took 0.021467208862304688s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Schemantra took 3.719329833984375e-05s
Believability | Calculation of trust value for Schemantra took 1.52587890625e-05s
INFO | --- Analysis for Schemantra took 600.2798507213593s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 0.00010085105895996094s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0007772445678710938s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 60.019941329956055s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.02133941650390625s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 4.887580871582031e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 1.430511474609375e-05s
INFO | --- Analysis for schemapedia took 600.2819862365723s
Availability | SPARQL endpoint availability check for Scholarometer took 0.00010514259338378906s
Availability | VoID file availability check for Scholarometer took 0.0008378028869628906s
Completeness | Calculation of interlinking completeness for Scholarometer took 60.02475666999817s
Reputation | Calculation of the PageRank for Scholarometer took 0.0223388671875s
Interlinking | Calculation of Degree of Connection for Scholarometer took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 0.00010538101196289062s
Believability | Calculation of trust value for Scholarometer took 1.3828277587890625e-05s
INFO | --- Analysis for scholarometer took 600.3076848983765s
Availability | SPARQL endpoint availability check for Science Commons took 0.00010848045349121094s
Availability | VoID file availability check for Science Commons took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for Science Commons took 60.026317834854126s
Reputation | Calculation of the PageRank for Science Commons took 0.02159571647644043s
Interlinking | Calculation of Degree of Connection for Science Commons took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Science Commons took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for Science Commons took 4.482269287109375e-05s
Believability | Calculation of trust value for Science Commons took 1.4543533325195312e-05s
INFO | --- Analysis for science_commons took 600.304750919342s
Availability | SPARQL endpoint availability check for ScienceWise took 9.417533874511719e-05s
Availability | VoID file availability check for ScienceWise took 0.00081634521484375s
Completeness | Calculation of interlinking completeness for ScienceWise took 60.02776050567627s
Reputation | Calculation of the PageRank for ScienceWise took 0.0214385986328125s
Interlinking | Calculation of Degree of Connection for ScienceWise took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for ScienceWise took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 4.458427429199219e-05s
Believability | Calculation of trust value for ScienceWise took 1.52587890625e-05s
INFO | --- Analysis for sciencewise took 600.3048396110535s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 9.131431579589844e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.000762939453125s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 60.02497959136963s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.02152228355407715s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 4.673004150390625e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 1.5735626220703125e-05s
INFO | --- Analysis for scoreboard took 600.2852709293365s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.00016164779663085938s
Availability | VoID file availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 60.02759575843811s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.021831989288330078s
Interlinking | Calculation of Degree of Connection for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.5299530029296875e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 2.0742416381835938e-05s
INFO | --- Analysis for SDDEC took 600.3003163337708s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.57763671875e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007457733154296875s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 60.02259659767151s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.021541595458984375s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.982948303222656e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.049041748046875e-05s
INFO | --- Analysis for SDG took 600.2956404685974s
Availability | SPARQL endpoint availability check for sears.com took 9.870529174804688e-05s
Availability | VoID file availability check for sears.com took 0.000743865966796875s
Completeness | Calculation of interlinking completeness for sears.com took 60.0272581577301s
Reputation | Calculation of the PageRank for sears.com took 0.02213764190673828s
Interlinking | Calculation of Degree of Connection for sears.com took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for sears.com took 8.320808410644531e-05s
Believability | Calculation of trust value for sears.com took 1.2874603271484375e-05s
INFO | --- Analysis for sears took 600.2885694503784s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 7.104873657226562e-05s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007526874542236328s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 60.02725267410278s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.02159714698791504s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 4.982948303222656e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.632110595703125e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0728836059570312e-05s
INFO | --- Analysis for sec-rdfabout took 600.2970538139343s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 0.00010585784912109375s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 60.03001046180725s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.02128744125366211s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 9.72747802734375e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 1.430511474609375e-05s
INFO | --- Analysis for secold took 600.3057942390442s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 9.322166442871094e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007863044738769531s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 60.027145862579346s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.024082422256469727s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 4.1484832763671875e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 1.4781951904296875e-05s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 600.3201768398285s
Availability | SPARQL endpoint availability check for semanlink took 0.0001087188720703125s
Availability | VoID file availability check for semanlink took 0.0007317066192626953s
Completeness | Calculation of interlinking completeness for semanlink took 60.02944898605347s
Reputation | Calculation of the PageRank for semanlink took 0.021272659301757812s
Interlinking | Calculation of Degree of Connection for semanlink took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.0001633167266845703s
Believability | Calculation of trust value for semanlink took 2.5033950805664062e-05s
INFO | --- Analysis for semanlink took 600.301943063736s
Availability | SPARQL endpoint availability check for Semantic Library took 0.00010085105895996094s
Availability | VoID file availability check for Semantic Library took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for Semantic Library took 60.02494215965271s
Reputation | Calculation of the PageRank for Semantic Library took 0.034201860427856445s
Interlinking | Calculation of Degree of Connection for Semantic Library took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for Semantic Library took 0.0012791156768798828s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 5.698204040527344e-05s
Believability | Calculation of trust value for Semantic Library took 2.6226043701171875e-05s
INFO | --- Analysis for semantic-library took 600.3206915855408s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 9.226799011230469e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.0007696151733398438s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 60.0229172706604s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.02141571044921875s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 4.673004150390625e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 1.5497207641601562e-05s
INFO | --- Analysis for semantic-profiling-network took 600.295889377594s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.0001723766326904297s
Availability | VoID file availability check for Semantic Universe Data took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 60.025694847106934s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.02135753631591797s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 4.124641418457031e-05s
Believability | Calculation of trust value for Semantic Universe Data took 1.3589859008789062e-05s
INFO | --- Analysis for semantic-universe took 600.3006002902985s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 0.00010967254638671875s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 60.025211811065674s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.021615982055664062s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.000141143798828125s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.430511474609375e-05s
INFO | --- Analysis for semantic-web-dog-food took 600.2886533737183s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 9.298324584960938e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0006921291351318359s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 60.02926778793335s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.021352291107177734s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 6.222724914550781e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 1.4066696166992188e-05s
INFO | --- Analysis for semantic-web-grundlagen took 600.3081939220428s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 9.107589721679688e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0007717609405517578s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 60.0269877910614s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.021572351455688477s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0008242130279541016s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 0.00010228157043457031s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 1.52587890625e-05s
INFO | --- Analysis for semantic-xbrl took 600.3052904605865s
Availability | SPARQL endpoint availability check for Semantic Bible took 0.00011348724365234375s
Availability | VoID file availability check for Semantic Bible took 0.0007643699645996094s
Completeness | Calculation of interlinking completeness for Semantic Bible took 60.02570176124573s
Reputation | Calculation of the PageRank for Semantic Bible took 0.021762371063232422s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 3.790855407714844e-05s
Believability | Calculation of trust value for Semantic Bible took 1.52587890625e-05s
INFO | --- Analysis for semantic_bible took 600.2917969226837s
Availability | SPARQL endpoint availability check for Semantic Quran took 9.989738464355469e-05s
Availability | VoID file availability check for Semantic Quran took 0.0007548332214355469s
Completeness | Calculation of interlinking completeness for Semantic Quran took 60.0282096862793s
Reputation | Calculation of the PageRank for Semantic Quran took 0.021352767944335938s
Interlinking | Calculation of Degree of Connection for Semantic Quran took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Semantic Quran took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Semantic Quran took 0.00010991096496582031s
Believability | Calculation of trust value for Semantic Quran took 1.5974044799804688e-05s
INFO | --- Analysis for semanticquran took 600.3046653270721s
Availability | SPARQL endpoint availability check for SemanticTweet took 0.0001087188720703125s
Availability | VoID file availability check for SemanticTweet took 0.0008687973022460938s
Completeness | Calculation of interlinking completeness for SemanticTweet took 60.0248486995697s
Reputation | Calculation of the PageRank for SemanticTweet took 0.022240638732910156s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.001331329345703125s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 0.00011134147644042969s
Believability | Calculation of trust value for SemanticTweet took 1.52587890625e-05s
INFO | --- Analysis for semantictweet took 600.2823076248169s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.57763671875e-05s
Availability | VoID file availability check for semanticweb.org took 0.0007512569427490234s
Completeness | Calculation of interlinking completeness for semanticweb.org took 60.020979166030884s
Reputation | Calculation of the PageRank for semanticweb.org took 0.021377086639404297s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 8.749961853027344e-05s
Believability | Calculation of trust value for semanticweb.org took 1.3589859008789062e-05s
INFO | --- Analysis for semanticweb-org took 600.2661666870117s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 9.72747802734375e-05s
Availability | VoID file availability check for Semantic CrunchBase took 0.0007572174072265625s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 60.026920557022095s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.021756649017333984s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 9.512901306152344e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 1.4781951904296875e-05s
INFO | --- Analysis for semsol-crunchbase took 600.2993109226227s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 0.00010251998901367188s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.0007531642913818359s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 60.02859950065613s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.021424055099487305s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 4.172325134277344e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 1.0251998901367188e-05s
INFO | --- Analysis for sensores-de-intellidomo took 600.3108954429626s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 9.226799011230469e-05s
Availability | VoID file availability check for SentimentWortschatz took 0.0007631778717041016s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 60.023775577545166s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.021557092666625977s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 5.14984130859375e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.430511474609375e-05s
INFO | --- Analysis for sentiws took 600.2998044490814s
Availability | SPARQL endpoint availability check for seoul-bike-data took 9.1552734375e-05s
Availability | VoID file availability check for seoul-bike-data took 0.0007367134094238281s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 60.02526926994324s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.021318912506103516s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 4.5299530029296875e-05s
Believability | Calculation of trust value for seoul-bike-data took 1.621246337890625e-05s
INFO | --- Analysis for seoul-bike-data took 600.3030796051025s
Availability | SPARQL endpoint availability check for Serendipity took 4.839897155761719e-05s
Availability | VoID file availability check for Serendipity took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for Serendipity took 60.031105756759644s
Reputation | Calculation of the PageRank for Serendipity took 0.022541046142578125s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0008699893951416016s
Interlinking | Calculation of Clustering coefficient for Serendipity took 9.107589721679688e-05s
Believability | Calculation of trust value for Serendipity took 1.0251998901367188e-05s
INFO | --- Analysis for serendipity took 600.2936058044434s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 9.703636169433594e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0007491111755371094s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 60.02785587310791s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.022143125534057617s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 5.1021575927734375e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 1.430511474609375e-05s
INFO | --- Analysis for Sherry_Wine took 600.3070321083069s
Availability | SPARQL endpoint availability check for Sherry Wine took 9.107589721679688e-05s
Availability | VoID file availability check for Sherry Wine took 0.00072479248046875s
Completeness | Calculation of interlinking completeness for Sherry Wine took 60.026973724365234s
Reputation | Calculation of the PageRank for Sherry Wine took 0.022096633911132812s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0008711814880371094s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 5.4836273193359375e-05s
Believability | Calculation of trust value for Sherry Wine took 1.5020370483398438e-05s
INFO | --- Analysis for Sherry_Wine_ took 600.2982521057129s
Availability | SPARQL endpoint availability check for Shoah victims? names took 9.632110595703125e-05s
Availability | VoID file availability check for Shoah victims? names took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 60.025160789489746s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.021453142166137695s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 5.435943603515625e-05s
Believability | Calculation of trust value for Shoah victims? names took 1.4781951904296875e-05s
INFO | --- Analysis for shoah-victims-names took 600.3081040382385s
Availability | SPARQL endpoint availability check for Person took 9.34600830078125e-05s
Availability | VoID file availability check for Person took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Person took 60.02588629722595s
Reputation | Calculation of the PageRank for Person took 0.028864622116088867s
Interlinking | Calculation of Degree of Connection for Person took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Person took 0.0010192394256591797s
Interlinking | Calculation of Clustering coefficient for Person took 4.506111145019531e-05s
Believability | Calculation of trust value for Person took 1.5735626220703125e-05s
INFO | --- Analysis for Shripriya_Dubey took 600.3054630756378s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 9.655952453613281e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0007348060607910156s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 60.02640175819397s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.02852034568786621s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 4.458427429199219e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 2.193450927734375e-05s
INFO | --- Analysis for Shutterstock took 600.2971444129944s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 0.00010704994201660156s
Availability | VoID file availability check for SIMILE Data Collection took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 60.02769637107849s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.02155327796936035s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 4.506111145019531e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 1.5020370483398438e-05s
INFO | --- Analysis for simile_data_collection took 600.307745218277s
Availability | SPARQL endpoint availability check for SIMPLE took 0.00010323524475097656s
Availability | VoID file availability check for SIMPLE took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for SIMPLE took 60.021965742111206s
Reputation | Calculation of the PageRank for SIMPLE took 0.021816492080688477s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 5.3882598876953125e-05s
Believability | Calculation of trust value for SIMPLE took 1.4781951904296875e-05s
INFO | --- Analysis for simple took 600.2885406017303s
Availability | SPARQL endpoint availability check for SITC-V4 took 4.935264587402344e-05s
Availability | VoID file availability check for SITC-V4 took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for SITC-V4 took 60.02494692802429s
Reputation | Calculation of the PageRank for SITC-V4 took 0.022144556045532227s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0009520053863525391s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 5.626678466796875e-05s
Believability | Calculation of trust value for SITC-V4 took 1.6689300537109375e-05s
INFO | --- Analysis for sitc-v4 took 600.2885191440582s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.00010061264038085938s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007433891296386719s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 60.02790951728821s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.021401643753051758s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.76837158203125e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.5497207641601562e-05s
INFO | --- Analysis for sli_galnet_rdf took 600.3026554584503s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 0.0001163482666015625s
Availability | VoID file availability check for Slideshare2RDF Server took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 60.024466037750244s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.02410745620727539s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 4.458427429199219e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 1.5974044799804688e-05s
INFO | --- Analysis for slideshare2rdf took 600.2905402183533s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 9.298324584960938e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.0007660388946533203s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 60.0268497467041s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.021445274353027344s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 5.125999450683594e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 1.4543533325195312e-05s
INFO | --- Analysis for slidewiki-rdf-sparql took 600.280467748642s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.00010275840759277344s
Availability | VoID file availability check for Linked Stage Graph took 0.0007271766662597656s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 60.02610516548157s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.021951675415039062s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 6.628036499023438e-05s
Believability | Calculation of trust value for Linked Stage Graph took 1.3828277587890625e-05s
INFO | --- Analysis for slod took 600.299920797348s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.000102996826171875s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007677078247070312s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 60.02671980857849s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.021633148193359375s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 4.1484832763671875e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.4781951904296875e-05s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 600.3086829185486s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 5.221366882324219e-05s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 60.024980783462524s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.02132701873779297s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00010466575622558594s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 1.5020370483398438e-05s
INFO | --- Analysis for Smart_POI_dataset took 600.2962403297424s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 0.00010442733764648438s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0007898807525634766s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 60.023930311203s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.02843475341796875s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 4.696846008300781e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 1.430511474609375e-05s
INFO | --- Analysis for smartlink took 600.3076255321503s
Availability | SPARQL endpoint availability check for SNIK took 0.00010228157043457031s
Availability | VoID file availability check for SNIK took 0.0007588863372802734s
Completeness | Calculation of interlinking completeness for SNIK took 60.02662777900696s
Reputation | Calculation of the PageRank for SNIK took 0.021451950073242188s
Interlinking | Calculation of Degree of Connection for SNIK took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for SNIK took 7.987022399902344e-05s
Believability | Calculation of trust value for SNIK took 8.821487426757812e-06s
INFO | --- Analysis for snik took 600.2997415065765s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 9.465217590332031e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 60.026365995407104s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.021986722946166992s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 4.76837158203125e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 1.0013580322265625e-05s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 600.3003313541412s
Availability | SPARQL endpoint availability check for SocialLink took 0.00010156631469726562s
Availability | VoID file availability check for SocialLink took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for SocialLink took 60.02421736717224s
Reputation | Calculation of the PageRank for SocialLink took 0.021296024322509766s
Interlinking | Calculation of Degree of Connection for SocialLink took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for SocialLink took 9.34600830078125e-05s
Believability | Calculation of trust value for SocialLink took 1.5497207641601562e-05s
INFO | --- Analysis for SocialLink took 600.2978236675262s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 0.00010061264038085938s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0007519721984863281s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 60.02620840072632s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.02229166030883789s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0009188652038574219s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 5.245208740234375e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 1.5497207641601562e-05s
INFO | --- Analysis for SocialRoles took 600.2970530986786s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 9.107589721679688e-05s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 60.02573370933533s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.021393537521362305s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 0.00011491775512695312s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.621246337890625e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 600.305389881134s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.00013828277587890625s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0008037090301513672s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 60.02782368659973s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.021361351013183594s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.553794860839844e-05s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.7404556274414062e-05s
INFO | --- Analysis for Soil_maps took 600.3118553161621s
Availability | SPARQL endpoint availability check for terrorrist ontology took 9.298324584960938e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0007634162902832031s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 60.02521777153015s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.021834135055541992s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 4.553794860839844e-05s
Believability | Calculation of trust value for terrorrist ontology took 1.4781951904296875e-05s
INFO | --- Analysis for somya_omer took 600.3075857162476s
Availability | SPARQL endpoint availability check for Sonclubcx took 9.34600830078125e-05s
Availability | VoID file availability check for Sonclubcx took 0.0007252693176269531s
Completeness | Calculation of interlinking completeness for Sonclubcx took 60.02405643463135s
Reputation | Calculation of the PageRank for Sonclubcx took 0.02146148681640625s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 2.5510787963867188e-05s
Believability | Calculation of trust value for Sonclubcx took 1.5020370483398438e-05s
INFO | --- Analysis for sonclubcx took 600.2831301689148s
Availability | SPARQL endpoint availability check for SORS took 9.989738464355469e-05s
Availability | VoID file availability check for SORS took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for SORS took 60.028610706329346s
Reputation | Calculation of the PageRank for SORS took 0.023737430572509766s
Interlinking | Calculation of Degree of Connection for SORS took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for SORS took 0.0001289844512939453s
Believability | Calculation of trust value for SORS took 1.4066696166992188e-05s
INFO | --- Analysis for sors took 600.2917628288269s
Availability | SPARQL endpoint availability check for Soudy České republiky took 0.00010561943054199219s
Availability | VoID file availability check for Soudy České republiky took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 60.0238676071167s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.022416114807128906s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 4.8160552978515625e-05s
Believability | Calculation of trust value for Soudy České republiky took 1.5020370483398438e-05s
INFO | --- Analysis for soudy--esk--republiky took 600.2829976081848s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 5.14984130859375e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.000732421875s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 60.024072885513306s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.02161264419555664s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 0.000110626220703125s
Believability | Calculation of trust value for southampton-ac-uk took 1.0251998901367188e-05s
INFO | --- Analysis for southampton-ac-uk took 600.289742231369s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 9.131431579589844e-05s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 60.017754554748535s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.02164149284362793s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 5.412101745605469e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 1.4543533325195312e-05s
INFO | --- Analysis for southampton-ac-uk-apps took 600.3170230388641s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 9.202957153320312e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 60.03984212875366s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.022560596466064453s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 0.00011920928955078125s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.5974044799804688e-05s
INFO | --- Analysis for southampton-ecs-eprints took 600.3600778579712s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.00014138221740722656s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 60.02544546127319s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.021663427352905273s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 4.839897155761719e-05s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 1.5735626220703125e-05s
INFO | --- Analysis for spanish-linguistic-datasets took 600.3033306598663s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.0001010894775390625s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.0007781982421875s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 60.02661108970642s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.021602153778076172s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 6.222724914550781e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 2.0265579223632812e-05s
INFO | --- Analysis for sparql-endpoint-status took 600.2983825206757s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 0.00012683868408203125s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 60.02621269226074s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.021163463592529297s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 4.458427429199219e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 1.4066696166992188e-05s
INFO | --- Analysis for spc-publikovan--s-kl took 600.2915325164795s
Availability | SPARQL endpoint availability check for SPQR took 9.918212890625e-05s
Availability | VoID file availability check for SPQR took 0.0007469654083251953s
Completeness | Calculation of interlinking completeness for SPQR took 60.02851748466492s
Reputation | Calculation of the PageRank for SPQR took 0.022542476654052734s
Interlinking | Calculation of Degree of Connection for SPQR took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for SPQR took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for SPQR took 3.528594970703125e-05s
Believability | Calculation of trust value for SPQR took 1.4781951904296875e-05s
INFO | --- Analysis for spqr took 600.2753443717957s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 0.00010800361633300781s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 60.02615189552307s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.021578550338745117s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 9.441375732421875e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 1.4781951904296875e-05s
INFO | --- Analysis for springernaturescigraph took 600.2859082221985s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.00010228157043457031s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.000736236572265625s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 60.02574396133423s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.021442890167236328s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.673004150390625e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.4781951904296875e-05s
INFO | --- Analysis for srcmf took 600.2881505489349s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 4.887580871582031e-05s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0008547306060791016s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 60.02819108963013s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.021709203720092773s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 7.152557373046875e-05s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 1.430511474609375e-05s
INFO | --- Analysis for ssf took 600.2889175415039s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.649162292480469e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 60.02670907974243s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.021291494369506836s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 5.3882598876953125e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 1.5497207641601562e-05s
INFO | --- Analysis for st-andrews-resource-lists took 600.2985408306122s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 0.00014400482177734375s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.0007991790771484375s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 60.022282123565674s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.021334409713745117s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 4.6253204345703125e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 1.0013580322265625e-05s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 600.3025553226471s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 9.942054748535156e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 60.02885103225708s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.021145105361938477s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.887580871582031e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.5020370483398438e-05s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 600.2895016670227s
Availability | SPARQL endpoint availability check for Stammbuch took 9.989738464355469e-05s
Availability | VoID file availability check for Stammbuch took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Stammbuch took 60.02635598182678s
Reputation | Calculation of the PageRank for Stammbuch took 0.021284103393554688s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 4.601478576660156e-05s
Believability | Calculation of trust value for Stammbuch took 1.9550323486328125e-05s
INFO | --- Analysis for Stammbuch took 600.2944324016571s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 9.632110595703125e-05s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0007510185241699219s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 60.02704477310181s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.0215911865234375s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00011897087097167969s
Believability | Calculation of trust value for statistics.data.gov.uk took 1.5020370483398438e-05s
INFO | --- Analysis for statistics-data-gov-uk took 600.2977313995361s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 9.989738464355469e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.0007638931274414062s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 60.02951622009277s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.02189922332763672s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 5.91278076171875e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 1.3589859008789062e-05s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 600.3121159076691s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 0.00010633468627929688s
Availability | VoID file availability check for statusnet-1w6-org took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 60.02859902381897s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.021162033081054688s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00011801719665527344s
Believability | Calculation of trust value for statusnet-1w6-org took 1.5735626220703125e-05s
INFO | --- Analysis for statusnet-1w6-org took 600.2885663509369s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 5.364418029785156e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 60.027623653411865s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.021213531494140625s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 7.700920104980469e-05s
Believability | Calculation of trust value for statusnet-20100-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-20100-org took 600.2956426143646s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 0.00011682510375976562s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 60.027475118637085s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.02174663543701172s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 9.560585021972656e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-alexandrefranke-com took 600.3017790317535s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 0.00012159347534179688s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 60.026777267456055s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.023597002029418945s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 0.00010061264038085938s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-atari-frosch-de took 600.3003535270691s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 9.250640869140625e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0008473396301269531s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 60.0271942615509s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.022127151489257812s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.52587890625e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 0.00011920928955078125s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-belfalas-org took 600.3061456680298s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 0.00010442733764648438s
Availability | VoID file availability check for statusnet-bka-li took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 60.02297759056091s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.02136993408203125s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00013589859008789062s
Believability | Calculation of trust value for statusnet-bka-li took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-bka-li took 600.2950663566589s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 0.00010609626770019531s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 60.028968811035156s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02150559425354004s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 5.2928924560546875e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 600.2971019744873s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 0.00012826919555664062s
Availability | VoID file availability check for statusnet-ced117-net took 0.0007538795471191406s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 60.025877475738525s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.0212705135345459s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 5.841255187988281e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-ced117-net took 600.2880833148956s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 0.0001010894775390625s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 60.02843904495239s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.02137446403503418s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 6.818771362304688e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 1.5497207641601562e-05s
INFO | --- Analysis for statusnet-chickenkiller-com took 600.3065204620361s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 9.989738464355469e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0007293224334716797s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 60.02063345909119s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.027328968048095703s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00013327598571777344s
Believability | Calculation of trust value for statusnet-chromic-org took 2.09808349609375e-05s
INFO | --- Analysis for statusnet-chromic-org took 600.3094878196716s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 0.00010991096496582031s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0008249282836914062s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 60.027796030044556s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.021419048309326172s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 0.00010061264038085938s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-cooleysekula-net took 600.3074834346771s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 0.00010395050048828125s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0008060932159423828s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 60.02539849281311s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.021505117416381836s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0010404586791992188s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 8.678436279296875e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-coreyavis-com took 600.2878367900848s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 0.00010323524475097656s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 60.02205419540405s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.0259401798248291s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 8.559226989746094e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-datenfahrt-org took 600.2943999767303s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 9.703636169433594e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 60.02690243721008s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.02128458023071289s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00011897087097167969s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 600.2871563434601s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 0.00010204315185546875s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.0007572174072265625s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 60.02403903007507s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.021470069885253906s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 7.843971252441406e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-deuxpi-ca took 499.10962986946106s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 7.772445678710938e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0008585453033447266s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 23.803173542022705s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.02129983901977539s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 6.222724914550781e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-doomicile-de took 160.56559133529663s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 0.00011777877807617188s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.307384729385376s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.021363258361816406s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.318092346191406e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-dtdns-net took 104.01499032974243s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.57763671875e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 22.818461894989014s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.02182745933532715s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 4.1961669921875e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-equestriarp-net took 151.7212779521942s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 5.1975250244140625e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 22.31882357597351s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.021495342254638672s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 8.96453857421875e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-exdc-net took 162.97897124290466s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 9.298324584960938e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 26.174350023269653s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.021311283111572266s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.369850158691406e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-fcac-com took 176.9084837436676s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.839897155761719e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.34148097038269043s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.02167367935180664s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.459785461425781e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-fcestrada-com took 123.72209978103638s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 9.298324584960938e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 27.784708499908447s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020904541015625s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00019931793212890625s
Believability | Calculation of trust value for statusnet-fragdev-com took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-fragdev-com took 187.58637166023254s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 9.226799011230469e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.30171799659729004s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.023541927337646484s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.939338684082031e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-freelish-us took 120.42166638374329s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 25.97809076309204s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.02164936065673828s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00012183189392089844s
Believability | Calculation of trust value for statusnet-gegeweb-org took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-gegeweb-org took 80.24771022796631s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 6.151199340820312e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.6810212135314941s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.02468585968017578s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0013909339904785156s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 9.799003601074219e-05s
Believability | Calculation of trust value for statusnet-glou-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-glou-org took 3.7421860694885254s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 7.772445678710938e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.24193811416625977s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.024170875549316406s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0012009143829345703s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00019979476928710938s
Believability | Calculation of trust value for statusnet-gomertronic-com took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-gomertronic-com took 4.1431849002838135s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 6.031990051269531e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0010552406311035156s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.28037595748901367s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.023067474365234375s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.001065969467163086s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00012826919555664062s
Believability | Calculation of trust value for statusnet-hackerposse-com took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-hackerposse-com took 3.3806488513946533s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.696846008300781e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.24991750717163086s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020948171615600586s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 5.435943603515625e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-hii-co-il took 3.2896578311920166s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 5.1021575927734375e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.25038695335388184s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.023858308792114258s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0010867118835449219s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 0.00013065338134765625s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 2.658787488937378s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.24729228019714355s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.02133774757385254s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0008723735809326172s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.580352783203125e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.474618911743164s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2434086799621582s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 3.981590270996094e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.467148542404175s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.3101215362548828s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.021007537841796875s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.8650970458984375e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.486178159713745s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 6.842613220214844e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.2570948600769043s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.021065950393676758s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011968612670898438s
Believability | Calculation of trust value for statusnet-jonkman-ca took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 3.2120704650878906s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 7.152557373046875e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.24243807792663574s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.02118229866027832s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0009853839874267578s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 0.0001227855682373047s
Believability | Calculation of trust value for statusnet-kaimi-cc took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-kaimi-cc took 2.435701370239258s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.673004150390625e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.2564690113067627s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.023754119873046875s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0009589195251464844s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 6.628036499023438e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-kathryl-fr took 2.3998944759368896s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 5.650520324707031e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.26463913917541504s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.022485971450805664s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0010657310485839844s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 5.7697296142578125e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-kenzoid-com took 3.2025256156921387s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 6.961822509765625e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.2635178565979004s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.02172541618347168s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0008046627044677734s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 8.630752563476562e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-keuser-fr took 2.317068576812744s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0012824535369873047s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.2577250003814697s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.021609783172607422s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 5.173683166503906e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.5101022720336914s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0003566741943359375s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.26217174530029297s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.023311376571655273s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0010843276977539062s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 8.606910705566406e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.5756475925445557s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 9.894371032714844e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.24229025840759277s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.02284979820251465s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 0.00013375282287597656s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 3.0827372074127197s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.24018239974975586s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.02202582359313965s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0010592937469482422s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00014138221740722656s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.431098222732544s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.23670053482055664s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02129364013671875s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.001020669937133789s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 8.630752563476562e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-ludost-net took 3.6941425800323486s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 6.079673767089844e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.27939295768737793s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.02135920524597168s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.52587890625e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0011355876922607422s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 0.0001266002655029297s
Believability | Calculation of trust value for statusnet-lydiastench-com took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-lydiastench-com took 2.363299608230591s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.2643427848815918s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.021416664123535156s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.555152893066406e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.373788833618164s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 9.226799011230469e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.2542304992675781s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.021015167236328125s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.0001533031463623047s
Believability | Calculation of trust value for statusnet-macno-org took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-macno-org took 2.5371193885803223s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.26951026916503906s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.021944284439086914s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 7.963180541992188e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.363787889480591s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 9.226799011230469e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.25015783309936523s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.02122354507446289s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 0.0001361370086669922s
Believability | Calculation of trust value for statusnet-maymay-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-maymay-net took 41.856298208236694s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.57763671875e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.26026105880737305s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.023737430572509766s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0010921955108642578s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00021648406982421875s
Believability | Calculation of trust value for statusnet-morphtown-de took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.4324002265930176s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 9.107589721679688e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.25479626655578613s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.021986722946166992s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.001220703125s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 0.00013184547424316406s
Believability | Calculation of trust value for statusnet-mrblog-nl took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-mrblog-nl took 2.478771924972534s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.262404203414917s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.021654367446899414s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 6.890296936035156e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-mulestable-net took 2.3669111728668213s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.25096917152404785s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.023211956024169922s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.7220458984375e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-my-status-tk took 2.5636603832244873s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0007598400115966797s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.24860119819641113s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.02518606185913086s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0013568401336669922s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00014972686767578125s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.543240785598755s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 0.00010228157043457031s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.23820710182189941s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.031009197235107422s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.001081705093383789s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 8.0108642578125e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.5394129753112793s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.27351927757263184s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.02160954475402832s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 7.414817810058594e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-otbm-fr took 2.4803719520568848s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.28153371810913086s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.02251458168029785s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 9.250640869140625e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.427161455154419s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 4.6253204345703125e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.23624753952026367s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.022251605987548828s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 5.1021575927734375e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-panda-id-au took 2.94813871383667s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 5.054473876953125e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.24868297576904297s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.021275043487548828s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 0.00010013580322265625s
Believability | Calculation of trust value for statusnet-piana-eu took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-piana-eu took 2.4365384578704834s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.26506781578063965s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.021100282669067383s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.987022399902344e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-planet-libre-org took 2.4423458576202393s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 9.322166442871094e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.2518272399902344s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.021253585815429688s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0010635852813720703s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.0002741813659667969s
Believability | Calculation of trust value for statusnet-postblue-info took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-postblue-info took 2.5979366302490234s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 8.487701416015625e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.2605702877044678s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.021083354949951172s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 7.05718994140625e-05s
Believability | Calculation of trust value for statusnet-progval-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-progval-net took 22.301527976989746s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.24187135696411133s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.021199464797973633s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0009541511535644531s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00013399124145507812s
Believability | Calculation of trust value for statusnet-qdnx-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-qdnx-org took 2.8479807376861572s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 9.202957153320312e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0014684200286865234s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.24552512168884277s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.021529436111450195s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.651878356933594e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-qth-fr took 5.4479005336761475s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.2498764991760254s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.02161097526550293s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0009129047393798828s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00024127960205078125s
Believability | Calculation of trust value for statusnet-quitter-se took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-quitter-se took 5.684076547622681s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.744529724121094e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.25209546089172363s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.022020816802978516s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0010066032409667969s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00013184547424316406s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.87563157081604s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 0.00011014938354492188s
Availability | VoID file availability check for statusnet-recit-org took 0.00048828125s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.2671973705291748s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.020853042602539062s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.9604644775390625e-05s
Believability | Calculation of trust value for statusnet-recit-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-recit-org took 12.734890460968018s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.00040984153747558594s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.25048375129699707s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.0216677188873291s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0008916854858398438s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00018334388732910156s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-russwurm-org took 3.130936861038208s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.25701332092285156s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.021570205688476562s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.988380432128906e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-samnoble-org took 4.700629234313965s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0003895759582519531s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.26470422744750977s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.021975278854370117s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0008370876312255859s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 9.036064147949219e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.39707612991333s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.2569139003753662s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.021783828735351562s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 0.00011229515075683594s
Believability | Calculation of trust value for statusnet-scoffoni-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.495234727859497s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.23706889152526855s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.021209001541137695s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0009164810180664062s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 7.939338684082031e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.4155173301696777s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 8.940696716308594e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.2641594409942627s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.023739099502563477s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.867813110351562e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-shnoulle-net took 3.258756399154663s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 7.319450378417969e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.25418949127197266s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.0209958553314209s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00021576881408691406s
Believability | Calculation of trust value for statusnet-skilledtests-com took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 2.746061086654663s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2506270408630371s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.02112889289855957s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.000110626220703125s
Believability | Calculation of trust value for statusnet-somsants-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-somsants-net took 2.344343662261963s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.2602198123931885s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.02295207977294922s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0008819103240966797s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00016260147094726562s
Believability | Calculation of trust value for statusnet-soucy-cc took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-soucy-cc took 12.886615991592407s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.57763671875e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.24888110160827637s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.02352166175842285s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.00106048583984375s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 7.867813110351562e-05s
Believability | Calculation of trust value for statusnet-spip-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-spip-org took 3.291431427001953s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 7.939338684082031e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0004222393035888672s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.26389503479003906s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.021473407745361328s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0009288787841796875s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 9.059906005859375e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-spraci-org took 5.738767623901367s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.00041747093200683594s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.26517343521118164s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.021198034286499023s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.52587890625e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.001016378402709961s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.0001442432403564453s
Believability | Calculation of trust value for statusnet-ssweeny-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 5.4728684425354s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0004086494445800781s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.26605868339538574s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.021991491317749023s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0010197162628173828s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.0002808570861816406s
Believability | Calculation of trust value for statusnet-status-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-status-net took 3.4970245361328125s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 6.031990051269531e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.00031828880310058594s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.26604652404785156s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.021563291549682617s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 6.890296936035156e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.4227280616760254s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.00041937828063964844s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.2723655700683594s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.023421049118041992s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007982254028320312s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 0.00010609626770019531s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 7.62939453125e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.4671173095703125s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0012822151184082031s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.24588441848754883s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.022876977920532227s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.0001308917999267578s
Believability | Calculation of trust value for statusnet-thelovebug-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-thelovebug-org took 2.4379048347473145s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.00039768218994140625s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.2776331901550293s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.022495746612548828s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.001234292984008789s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 0.00010776519775390625s
Believability | Calculation of trust value for statusnet-thornton2-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-thornton2-com took 4.997662305831909s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 0.00011014938354492188s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.2619616985321045s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.021554946899414062s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.52587890625e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0010917186737060547s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00013446807861328125s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.6273350715637207s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.887580871582031e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.25501155853271484s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.0226442813873291s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0011713504791259766s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 5.698204040527344e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-tl1n-com took 3.832146167755127s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.673004150390625e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.250762939453125s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.021335840225219727s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0008959770202636719s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 8.368492126464844e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.5957939624786377s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0007815361022949219s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.2532992362976074s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.024647235870361328s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.52587890625e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0011949539184570312s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 5.602836608886719e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-uni-siegen-de took 3.282167911529541s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.601478576660156e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.3546321392059326s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.021981477737426758s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0009930133819580078s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 5.698204040527344e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for steak took 3.4752073287963867s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 0.00010371208190917969s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.30212855339050293s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.02258443832397461s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0011324882507324219s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 7.104873657226562e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 8.821487426757812e-06s
INFO | --- Analysis for stitch-rameau took 4.474311828613281s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.892406702041626s
Availability | VoID file availability check for Stone Tech Square took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.2794311046600342s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.021831512451171875s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.52587890625e-05s
Believability | Calculation of trust value for Stone Tech Square took 8.344650268554688e-06s
INFO | --- Analysis for stone-tech-square-data took 5.878579378128052s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 4.9114227294921875e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.3023836612701416s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.02233576774597168s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 3.2901763916015625e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 1.3113021850585938e-05s
INFO | --- Analysis for strukturovan--popisy-z-fda took 3.957747459411621s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.5052320957183838s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0004973411560058594s
Extra | Recovery of all triples for STW Thesaurus for Economics took 16.906360387802124s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.1763086318969727s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.6799910068511963s
Interoperability | New terms check for STW Thesaurus for Economics took 1.8831191062927246s
Versatility | Languages check for STW Thesaurus for Economics took 1.915799617767334s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.6218972206115723s
Security | Check HTTPS for STW Thesaurus for Economics took 0.16315126419067383s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.26276612281799316s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.25366973876953125s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.2549762725830078s
License | MR license check for STW Thesaurus for Economics took 0.25748562812805176s
License | HR license check for STW Thesaurus for Economics took 2.7651708126068115s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.24234604835510254s
Understandability | Number of label check for STW Thesaurus for Economics took 0.8060729503631592s
Understandability | URI regex check for STW Thesaurus for Economics took 0.456972599029541s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.27644848823547363s
Verifiability | Authors check for STW Thesaurus for Economics took 0.2860097885131836s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.2797281742095947s
Performance | Throughput check for STW Thesaurus for Economics took 11.23859715461731s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7638604640960693s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.27514100074768066s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.2528676986694336s
Interlinking | skos check for STW Thesaurus for Economics took 0.36643171310424805s
Interlinking | skos check for STW Thesaurus for Economics took 0.3079826831817627s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.24436092376708984s
Currency | Creation date check for STW Thesaurus for Economics took 0.5222771167755127s
Currency | Modification date check for STW Thesaurus for Economics took 0.5531704425811768s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 8.772737264633179s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 5.096276044845581s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.2732865810394287s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.2784590721130371s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.2677123546600342s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 4.707873106002808s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0655198097229004s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.4502458572387695s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.24541330337524414s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.573941707611084s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 1.9153227806091309s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.4840874671936035s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.618406057357788s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6613216400146484s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.25106120109558105s
Security | Sign check for STW Thesaurus for Economics took 0.28218793869018555s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 2853.148582458496s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.9675917625427246s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.022272109985351562s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0008847713470458984s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00014638900756835938s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 3.205592632293701s
Believability | Calculation of trust value for STW Thesaurus for Economics took 9.059906005859375e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 2958.0368456840515s
Availability | SPARQL endpoint availability check for SudershanTech took 4.863739013671875e-05s
Availability | VoID file availability check for SudershanTech took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.29549384117126465s
Reputation | Calculation of the PageRank for SudershanTech took 0.02145218849182129s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 4.7206878662109375e-05s
Believability | Calculation of trust value for SudershanTech took 8.58306884765625e-06s
INFO | --- Analysis for SudershanTech took 3.2004337310791016s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.8327414989471436s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.3398747444152832s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.024050235748291016s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.000988006591796875s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 6.365776062011719e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 1.239776611328125e-05s
INFO | --- Analysis for sudocfr took 7.889399290084839s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 1.0625016689300537s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0006628036499023438s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 22.741543292999268s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.7070844173431396s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.5898034572601318s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 3.0167572498321533s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 2.8064942359924316s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.1812849044799805s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5473732948303223s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5681242942810059s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5626912117004395s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5278973579406738s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 7.769529581069946s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.6006319522857666s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.689530611038208s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.0966484546661377s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5492782592773438s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5651743412017822s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5378375053405762s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.893905401229858s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 3.337860107421875e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5513150691986084s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5757160186767578s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5936071872711182s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5767958164215088s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5428225994110107s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.099987268447876s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.1133005619049072s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 36.627373695373535s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5343976020812988s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5220389366149902s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5418472290039062s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 3.182983636856079s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.3895435333251953s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.5362598896026611s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 26.990346431732178s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.73697543144226s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.4018578529358s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 19.712281227111816s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 3.0946216583251953s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.877350330352783s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.538611888885498s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4628.238169193268s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 1.137439250946045s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.02266693115234375s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 0.0001575946807861328s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 9.059906005859375e-06s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 8163.716878890991s
Availability | SPARQL endpoint availability check for Surge Radio took 9.226799011230469e-05s
Availability | VoID file availability check for Surge Radio took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.3459041118621826s
Reputation | Calculation of the PageRank for Surge Radio took 0.021070003509521484s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 9.059906005859375e-05s
Believability | Calculation of trust value for Surge Radio took 7.867813110351562e-06s
INFO | --- Analysis for surge-radio took 4.0734124183654785s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 9.226799011230469e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0007579326629638672s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.3077101707458496s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.0213167667388916s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 4.0531158447265625e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 1.2159347534179688e-05s
INFO | --- Analysis for SWAT took 60.94845914840698s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.506111145019531e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.4621918201446533s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.3104534149169922s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020954132080078125s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 7.915496826171875e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 1.1444091796875e-05s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.53025484085083s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.0055880546569824s
Availability | VoID file availability check for SweFN-RDF took 0.0007426738739013672s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.312572717666626s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.02159285545349121s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 4.00543212890625e-05s
Believability | Calculation of trust value for SweFN-RDF took 1.33514404296875e-05s
INFO | --- Analysis for swefn-rdf took 6.8243958950042725s
Availability | SPARQL endpoint availability check for SwetoDblp took 6.699562072753906e-05s
Availability | VoID file availability check for SwetoDblp took 0.0009191036224365234s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.38620471954345703s
Reputation | Calculation of the PageRank for SwetoDblp took 0.02103447914123535s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 4.601478576660156e-05s
Believability | Calculation of trust value for SwetoDblp took 1.1920928955078125e-05s
INFO | --- Analysis for sweto-dblp took 23.583486080169678s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.5130681991577148s
Availability | VoID file availability check for Swift Vocabulary took 0.0006029605865478516s
Extra | Recovery of all triples for Swift Vocabulary took 2.2034752368927s
Performance | Total latancy measurement for Swift Vocabulary took 1.0198523998260498s
Amount of data | Number of triples check for Swift Vocabulary took 0.1812584400177002s
Interoperability | New terms check for Swift Vocabulary took 1.5158071517944336s
Versatility | Languages check for Swift Vocabulary took 0.17466998100280762s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.15966582298278809s
Interpretability | RDF structures check for Swift Vocabulary took 0.191270112991333s
Versatility | Serialization formats check for Swift Vocabulary took 0.18329977989196777s
Availability | RDF dump link check for Swift Vocabulary took 0.1919269561767578s
License | MR license check for Swift Vocabulary took 0.21845102310180664s
License | HR license check for Swift Vocabulary took 0.21361589431762695s
Amount of data | Number of property check for Swift Vocabulary took 0.22842860221862793s
Understandability | Number of label check for Swift Vocabulary took 0.19793391227722168s
Understandability | URI regex check for Swift Vocabulary took 0.36259913444519043s
Understandability | Vocabs check for Swift Vocabulary took 0.22978448867797852s
Verifiability | Authors check for Swift Vocabulary took 0.21626853942871094s
Verifiability | Publishers check for Swift Vocabulary took 0.21393132209777832s
Performance | Throughput check for Swift Vocabulary took 10.470759868621826s
Amount of data | Check the number of entities for Swift Vocabulary took 0.00010514259338378906s
Verifiability | Contribs. check for Swift Vocabulary took 0.18785834312438965s
Interlinking | sameAs chians check for Swift Vocabulary took 0.20753169059753418s
Interlinking | skos check for Swift Vocabulary took 0.18810701370239258s
Interlinking | skos check for Swift Vocabulary took 0.2083127498626709s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.21539878845214844s
Currency | Creation date check for Swift Vocabulary took 0.4050631523132324s
Currency | Modification date check for Swift Vocabulary took 0.4084646701812744s
Rep.Conc. | URIs length for Swift Vocabulary took 0.8087682723999023s
Interoperability | New vocabularies check for Swift Vocabulary took 5.4836273193359375e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.19144725799560547s
Accuracy | Check Functional Property for Swift Vocabulary took 0.21053838729858398s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.21542787551879883s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.37267303466796875s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.003704071044921875s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.037757158279418945s
Consistency | Disjoint class check for Swift Vocabulary took 0.20531487464904785s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.48470473289489746s
Consistency | Misplaced classes for Swift Vocabulary took 0.30616068840026855s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.6572906970977783s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.3791801929473877s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.5929794311523438s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.02758312225341797s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.1735990047454834s
Security | Sign check for Swift Vocabulary took 0.15862154960632324s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 946.7431969642639s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.4734370708465576s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.022122621536254883s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 8.845329284667969e-05s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 1.9073486328125e-06s
Believability | Calculation of trust value for Swift Vocabulary took 1.33514404296875e-05s
INFO | --- Analysis for Swift took 993.6270093917847s
Availability | SPARQL endpoint availability check for SymbolicData took 4.38690185546875e-05s
Availability | VoID file availability check for SymbolicData took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.3333778381347656s
Reputation | Calculation of the PageRank for SymbolicData took 0.021401643753051758s
Interlinking | Calculation of Degree of Connection for SymbolicData took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for SymbolicData took 0.0008697509765625s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 3.814697265625e-05s
Believability | Calculation of trust value for SymbolicData took 1.2874603271484375e-05s
INFO | --- Analysis for symbolicdata took 4.013876676559448s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 4.7206878662109375e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.35872793197631836s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.021008729934692383s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.528594970703125e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 1.1920928955078125e-05s
INFO | --- Analysis for symptoms-in-chinese took 4.501795291900635s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.4487571716308594s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0007958412170410156s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.5131127834320068s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.9009835720062256s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 7.899016857147217s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 20.668944358825684s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.19441556930541992s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 4.02564263343811s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.12402582168579102s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.5746550559997559s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.2038254737854004s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.5059003829956055s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.43953585624694824s
License | HR license check for National Digital Data Archive of Hungary (partial) took 53.70870041847229s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.5448462963104248s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 38.66547131538391s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3655552864074707s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.22620582580566406s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.1803576946258545s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.16190171241760254s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.489395141601562s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 7.581710815429688e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.7372493743896484s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.8125765323638916s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.6023869514465332s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5327718257904053s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.5445191860198975s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 3.1485579013824463s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 2.821732997894287s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 69.62981462478638s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.1998298168182373s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.1934499740600586s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.1774153709411621s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.23726463317871094s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0019288063049316406s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0015952587127685547s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.17835187911987305s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 48.76043367385864s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.3035316467285156s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.6821255683898926s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.3859162330627441s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 49.60412383079529s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.003923892974853516s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.42102742195129395s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.18066644668579102s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 9.439932346343994s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.37793397903442383s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.023752927780151367s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0008540153503417969s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 0.00010657310485839844s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.430511474609375e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 1.33514404296875e-05s
INFO | --- Analysis for sztaki-lod took 497.6399898529053s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 9.34600830078125e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.5411605834960938s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.022420644760131836s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 7.939338684082031e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 1.239776611328125e-05s
INFO | --- Analysis for t4gm-info took 3.6096222400665283s
Availability | SPARQL endpoint availability check for tags2con delicious took 9.226799011230469e-05s
Availability | VoID file availability check for tags2con delicious took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.5416245460510254s
Reputation | Calculation of the PageRank for tags2con delicious took 0.02165699005126953s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0009310245513916016s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 5.269050598144531e-05s
Believability | Calculation of trust value for tags2con delicious took 1.1444091796875e-05s
INFO | --- Analysis for tags2con-delicious took 45.48888969421387s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 263.18275809288025s
Availability | VoID file availability check for Taiwan geographic names took 0.0008590221405029297s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.37703394889831543s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.02160334587097168s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 0.00017547607421875s
Believability | Calculation of trust value for Taiwan geographic names took 1.2636184692382812e-05s
INFO | --- Analysis for taiwan-geographic-names took 667.3107323646545s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 0.00015163421630859375s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.4178333282470703s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.021239042282104492s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.417533874511719e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 1.239776611328125e-05s
INFO | --- Analysis for talis-openlibrary took 5.081128358840942s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.8880243301391602s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.3576090335845947s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.022623300552368164s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.0001270771026611328s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 1.239776611328125e-05s
INFO | --- Analysis for taxonconcept took 13.888901472091675s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 9.441375732421875e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.3197200298309326s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.021312236785888672s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.416175842285156e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.3113021850585938e-05s
INFO | --- Analysis for taxonconcept-assets took 3.333998680114746s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 8.940696716308594e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.28722429275512695s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.02171158790588379s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 7.367134094238281e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 1.1920928955078125e-05s
INFO | --- Analysis for taxonconcept-occurences took 3.381582498550415s
Availability | SPARQL endpoint availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.4489727020263672s
Availability | VoID file availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0005958080291748047s
Extra | Recovery of all triples for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 4.2239344120025635s
Performance | Total latancy measurement for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.9248323440551758s
Amount of data | Number of triples check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 23.626601934432983s
Interoperability | New terms check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 12.968558549880981s
Versatility | Languages check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 60.893505334854126s
Interpretability | Number of blank nodes check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 7.858835220336914s
Interpretability | RDF structures check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.2694129943847656s
Versatility | Serialization formats check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.8637807369232178s
Availability | RDF dump link check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.7277824878692627s
License | MR license check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.949425458908081s
License | HR license check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 60.50740599632263s
Amount of data | Number of property check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.31946396827697754s
Understandability | Number of label check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 7.007770538330078s
Understandability | URI regex check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.5629899501800537s
Understandability | Vocabs check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.2290487289428711s
Verifiability | Authors check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.18242120742797852s
Verifiability | Publishers check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.1839585304260254s
Performance | Throughput check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 10.89956283569336s
Amount of data | Check the number of entities for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.023717641830444336s
Verifiability | Contribs. check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.24122238159179688s
Interlinking | sameAs chians check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.6051204204559326s
Interlinking | skos check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.3180844783782959s
Interlinking | skos check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.24370789527893066s
Timeliness | dataset update frequency check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.0166614055633545s
Currency | Creation date check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.6550867557525635s
Currency | Modification date check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.264209508895874s
Rep.Conc. | URIs length for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 36.26156282424927s
Interoperability | New vocabularies check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 20.56797194480896s
Consistency | Deprecated classes/propertiers check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.21032023429870605s
Accuracy | Check Functional Property for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.5383555889129639s
Accuracy | Check Inverse Functional Property for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.5030193328857422s
Accuracy | Check Empty annotation labels for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.549712896347046s
Accuracy | Check White space in annotation for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.030455350875854492s
Accuracy | Check Datatype consistency for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.02940654754638672s
Consistency | Disjoint class check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.269977331161499s
Consistency | Check Misplaced properties for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 13.193295001983643s
Consistency | Misplaced classes for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.5302886962890625s
Consistency | Check Ontology hijacking for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 2.3045129776000977s
Consistency | Check Invalid usage of undefined classes for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.3825056552886963s
Consistency | Check Invalid usage of undefined properties for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 14.182077884674072s
Conciseness | Check Extensional conciseness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.03312063217163086s
Conciseness | Check Intensional conciseness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.4100685119628906s
Security | Sign check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.940993070602417s
Availability | Check URIs Dereferenciability for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 10.368380546569824s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.43294286727905273s
Reputation | Calculation of the PageRank for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.021790027618408203s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 6.0558319091796875e-05s
Interoperability | Check the re-using of existing vocabs for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 19.635783672332764s
Believability | Calculation of trust value for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.6927719116210938e-05s
INFO | --- Analysis for taxref-ld took 1123.50359416008s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 262.28845047950745s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0007357597351074219s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.33544445037841797s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.021404743194580078s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 4.267692565917969e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.33514404296875e-05s
INFO | --- Analysis for tcga took 541.4588317871094s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3855152130126953s
Availability | VoID file availability check for TCGA Roadmap took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.32715821266174316s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.022854328155517578s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 8.487701416015625e-05s
Believability | Calculation of trust value for TCGA Roadmap took 7.867813110351562e-06s
INFO | --- Analysis for tcga-roadmap took 6.581812620162964s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.6440703868865967s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.3322291374206543s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.021303415298461914s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0008716583251953125s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.0001220703125s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 1.1444091796875e-05s
INFO | --- Analysis for tcmgenedit_dataset took 137.3577344417572s
Availability | SPARQL endpoint availability check for TDS took 9.679794311523438e-05s
Availability | VoID file availability check for TDS took 0.0012600421905517578s
Completeness | Calculation of interlinking completeness for TDS took 0.3713366985321045s
Reputation | Calculation of the PageRank for TDS took 0.021071434020996094s
Interlinking | Calculation of Degree of Connection for TDS took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for TDS took 4.839897155761719e-05s
Believability | Calculation of trust value for TDS took 1.1682510375976562e-05s
INFO | --- Analysis for tds took 5.537886381149292s
Availability | SPARQL endpoint availability check for TEKORD took 4.792213439941406e-05s
Availability | VoID file availability check for TEKORD took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for TEKORD took 0.3210728168487549s
Reputation | Calculation of the PageRank for TEKORD took 0.021036863327026367s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.863739013671875e-05s
Believability | Calculation of trust value for TEKORD took 1.239776611328125e-05s
INFO | --- Analysis for tekord took 5.809182643890381s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 2.3905787467956543s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.30846595764160156s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.021185874938964844s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00011467933654785156s
Believability | Calculation of trust value for Telegraphis Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for telegraphis took 9.37122368812561s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.458427429199219e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0008091926574707031s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.3645651340484619s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.021425724029541016s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 8.082389831542969e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 1.3113021850585938e-05s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 15.16847848892212s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 9.036064147949219e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.3542964458465576s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.021314382553100586s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 3.2901763916015625e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 3.9465339183807373s
Availability | SPARQL endpoint availability check for Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for Ontology took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for Ontology took 0.3411741256713867s
Reputation | Calculation of the PageRank for Ontology took 0.02131819725036621s
Interlinking | Calculation of Degree of Connection for Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.552436828613281e-05s
Believability | Calculation of trust value for Ontology took 8.344650268554688e-06s
INFO | --- Analysis for Terrorist_attack took 4.00271463394165s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.9114227294921875e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.30628061294555664s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.02102065086364746s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.337860107421875e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 1.1444091796875e-05s
INFO | --- Analysis for Terrorist_Attack_1 took 3.282330274581909s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 4.4345855712890625e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.3082084655761719s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.021237850189208984s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.3855438232421875e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.1920928955078125e-05s
INFO | --- Analysis for Tesla_Deaths took 4.933002710342407s
Availability | SPARQL endpoint availability check for test took 4.410743713378906e-05s
Availability | VoID file availability check for test took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for test took 0.33623194694519043s
Reputation | Calculation of the PageRank for test took 0.021314144134521484s
Interlinking | Calculation of Degree of Connection for test took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for test took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for test took 3.218650817871094e-05s
Believability | Calculation of trust value for test took 1.0967254638671875e-05s
INFO | --- Analysis for test took 3.0303962230682373s
Availability | SPARQL endpoint availability check for Test took 4.410743713378906e-05s
Availability | VoID file availability check for Test took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Test took 0.2654752731323242s
Reputation | Calculation of the PageRank for Test took 0.02111363410949707s
Interlinking | Calculation of Degree of Connection for Test took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Test took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Test took 3.266334533691406e-05s
Believability | Calculation of trust value for Test took 1.52587890625e-05s
INFO | --- Analysis for Test took 2.8402693271636963s
Availability | SPARQL endpoint availability check for test-svu took 20.189609050750732s
Availability | VoID file availability check for test-svu took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for test-svu took 0.31485748291015625s
Reputation | Calculation of the PageRank for test-svu took 0.02103590965270996s
Interlinking | Calculation of Degree of Connection for test-svu took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for test-svu took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for test-svu took 4.220008850097656e-05s
Believability | Calculation of trust value for test-svu took 1.2159347534179688e-05s
INFO | --- Analysis for test-svu took 53.16916060447693s
Availability | SPARQL endpoint availability check for Test took 4.553794860839844e-05s
Availability | VoID file availability check for Test took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Test took 0.30324506759643555s
Reputation | Calculation of the PageRank for Test took 0.02339029312133789s
Interlinking | Calculation of Degree of Connection for Test took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Test took 0.0012984275817871094s
Interlinking | Calculation of Clustering coefficient for Test took 4.553794860839844e-05s
Believability | Calculation of trust value for Test took 1.1682510375976562e-05s
INFO | --- Analysis for Test_ took 3.035537004470825s
Availability | SPARQL endpoint availability check for xxxxx took 260.988374710083s
Availability | VoID file availability check for xxxxx took 0.0008063316345214844s
Completeness | Calculation of interlinking completeness for xxxxx took 0.32563018798828125s
Reputation | Calculation of the PageRank for xxxxx took 0.022530555725097656s
Interlinking | Calculation of Degree of Connection for xxxxx took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.001129150390625s
Interlinking | Calculation of Clustering coefficient for xxxxx took 8.0108642578125e-05s
Believability | Calculation of trust value for xxxxx took 1.2874603271484375e-05s
INFO | --- Analysis for testee took 798.2352662086487s
Availability | SPARQL endpoint availability check for Texai Lexicon took 5.125999450683594e-05s
Availability | VoID file availability check for Texai Lexicon took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.35225892066955566s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.021316051483154297s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0009961128234863281s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 3.838539123535156e-05s
Believability | Calculation of trust value for Texai Lexicon took 1.2159347534179688e-05s
INFO | --- Analysis for texai_lexicon took 4.2702789306640625s
Availability | SPARQL endpoint availability check for tharawat magazine took 9.083747863769531e-05s
Availability | VoID file availability check for tharawat magazine took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.3031313419342041s
Reputation | Calculation of the PageRank for tharawat magazine took 0.021352291107177734s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00011515617370605469s
Believability | Calculation of trust value for tharawat magazine took 1.2159347534179688e-05s
INFO | --- Analysis for tharawat-magazine-com took 3.881460189819336s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 1.466939926147461s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.3592803478240967s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.021106243133544922s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.457069396972656e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 1.239776611328125e-05s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 8.271817684173584s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 3.3510756492614746s
Availability | VoID file availability check for The European Library Open Dataset took 0.0007843971252441406s
Extra | Recovery of all triples for The European Library Open Dataset took 6.964739084243774s
Performance | Total latancy measurement for The European Library Open Dataset took 15.987073421478271s
Amount of data | Number of triples check for The European Library Open Dataset took 65.09762787818909s
Interoperability | New terms check for The European Library Open Dataset took 60.258233308792114s
Versatility | Languages check for The European Library Open Dataset took 3.187056303024292s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 3.197683811187744s
Interpretability | RDF structures check for The European Library Open Dataset took 3.203840494155884s
Versatility | Serialization formats check for The European Library Open Dataset took 3.2021775245666504s
Availability | RDF dump link check for The European Library Open Dataset took 3.199772596359253s
License | MR license check for The European Library Open Dataset took 3.201470375061035s
License | HR license check for The European Library Open Dataset took 3.195906639099121s
Amount of data | Number of property check for The European Library Open Dataset took 3.20351243019104s
Understandability | Number of label check for The European Library Open Dataset took 3.761317491531372s
Understandability | URI regex check for The European Library Open Dataset took 6.412965297698975s
Understandability | Vocabs check for The European Library Open Dataset took 3.1995034217834473s
Verifiability | Authors check for The European Library Open Dataset took 3.2045183181762695s
Verifiability | Publishers check for The European Library Open Dataset took 3.192669153213501s
Performance | Throughput check for The European Library Open Dataset took 31.971580028533936s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.200241088867188e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 3.2048802375793457s
Interlinking | sameAs chians check for The European Library Open Dataset took 3.295978307723999s
Interlinking | skos check for The European Library Open Dataset took 3.2428557872772217s
Interlinking | skos check for The European Library Open Dataset took 3.2317404747009277s
Timeliness | dataset update frequency check for The European Library Open Dataset took 3.24245285987854s
Currency | Creation date check for The European Library Open Dataset took 6.375701427459717s
Currency | Modification date check for The European Library Open Dataset took 6.400063514709473s
Rep.Conc. | URIs length for The European Library Open Dataset took 124.00246787071228s
Interoperability | New vocabularies check for The European Library Open Dataset took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 3.194934606552124s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 3.4944190979003906s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.026506423950195312s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.03007960319519043s
Consistency | Disjoint class check for The European Library Open Dataset took 3.197615623474121s
Consistency | Check Misplaced properties for The European Library Open Dataset took 67.2550458908081s
Consistency | Misplaced classes for The European Library Open Dataset took 3.2711739540100098s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 4.971969127655029s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.3797860145568848s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 65.77070474624634s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.037744760513305664s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 3.205789566040039s
Security | Sign check for The European Library Open Dataset took 3.199928045272827s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 11.127665042877197s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.6145451068878174s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.026429176330566406s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.52587890625e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0010120868682861328s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 9.34600830078125e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 1.3113021850585938e-05s
INFO | --- Analysis for the-european-library-open-dataset took 921.0049021244049s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.02718901634216s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0007305145263671875s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.34210777282714844s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.025873184204101562s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.0001201629638671875s
Believability | Calculation of trust value for The Eurostat Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for the-eurostat-linked-data took 243.1446750164032s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 4.410743713378906e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.32254505157470703s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.021617650985717773s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0008087158203125s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 3.504753112792969e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.2636184692382812e-05s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 3.7635295391082764s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.601478576660156e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0007622241973876953s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.3390829563140869s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.021382808685302734s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.557868957519531e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 1.2159347534179688e-05s
INFO | --- Analysis for the-living-lod-cloud took 51.79329323768616s
Availability | SPARQL endpoint availability check for The View From took 5.443310499191284s
Availability | VoID file availability check for The View From took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for The View From took 0.3238656520843506s
Reputation | Calculation of the PageRank for The View From took 0.021310091018676758s
Interlinking | Calculation of Degree of Connection for The View From took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for The View From took 8.869171142578125e-05s
Believability | Calculation of trust value for The View From took 7.3909759521484375e-06s
INFO | --- Analysis for the-view-from took 12.014937400817871s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.49174404144287s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0007078647613525391s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.5095903873443604s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020937204360961914s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 4.1961669921875e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.1682510375976562e-05s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 74.07551956176758s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.024147033691406s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.3339848518371582s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.022705554962158203s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.886222839355469e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 7.3909759521484375e-06s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 103.63298058509827s
Availability | SPARQL endpoint availability check for The Content Wrangler took 9.012222290039062e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.3617374897003174s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.02123880386352539s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.000118255615234375s
Believability | Calculation of trust value for The Content Wrangler took 7.62939453125e-06s
INFO | --- Analysis for thecontentwrangler-com took 3.5878524780273438s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 5.125999450683594e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0007908344268798828s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.32291197776794434s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.021274089813232422s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.409385681152344e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 8.58306884765625e-06s
INFO | --- Analysis for thesaurus-datenwissen took 3.054687261581421s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.7639844417572021s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.3329305648803711s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.022106647491455078s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0012514591217041016s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 0.0001125335693359375s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 1.1205673217773438e-05s
INFO | --- Analysis for thesaurus-w took 5.4736549854278564s
Availability | SPARQL endpoint availability check for theses.fr took 4.5299530029296875e-05s
Availability | VoID file availability check for theses.fr took 0.0008995532989501953s
Completeness | Calculation of interlinking completeness for theses.fr took 0.33156681060791016s
Reputation | Calculation of the PageRank for theses.fr took 0.021091699600219727s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for theses.fr took 5.507469177246094e-05s
Believability | Calculation of trust value for theses.fr took 1.52587890625e-05s
INFO | --- Analysis for thesesfr took 5.011667728424072s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 9.226799011230469e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.3100407123565674s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.023013830184936523s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.218650817871094e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.790855407714844e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.239776611328125e-05s
INFO | --- Analysis for Thinkphile took 3.046215057373047s
Availability | SPARQL endpoint availability check for ThIST took 265.1057469844818s
Availability | VoID file availability check for ThIST took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for ThIST took 0.6120290756225586s
Reputation | Calculation of the PageRank for ThIST took 0.021504640579223633s
Interlinking | Calculation of Degree of Connection for ThIST took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for ThIST took 9.489059448242188e-05s
Believability | Calculation of trust value for ThIST took 1.239776611328125e-05s
INFO | --- Analysis for thist took 564.530287027359s
Availability | SPARQL endpoint availability check for TIP took 40.035080909729004s
Availability | VoID file availability check for TIP took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for TIP took 0.3143422603607178s
Reputation | Calculation of the PageRank for TIP took 0.02167987823486328s
Interlinking | Calculation of Degree of Connection for TIP took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00011897087097167969s
Believability | Calculation of trust value for TIP took 1.2159347534179688e-05s
INFO | --- Analysis for tip took 103.42722177505493s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 5.459785461425781e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0008006095886230469s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.6071727275848389s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.020877838134765625s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.3855438232421875e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 8.344650268554688e-06s
INFO | --- Analysis for TOPMODEL took 39.82652139663696s
Availability | SPARQL endpoint availability check for Tourpedia took 4.4345855712890625e-05s
Availability | VoID file availability check for Tourpedia took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.34033703804016113s
Reputation | Calculation of the PageRank for Tourpedia took 0.021312475204467773s
Interlinking | Calculation of Degree of Connection for Tourpedia took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Tourpedia took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 3.314018249511719e-05s
Believability | Calculation of trust value for Tourpedia took 8.106231689453125e-06s
INFO | --- Analysis for tourpedia took 3.97072434425354s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.7258341312408447s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.2794640064239502s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.02322530746459961s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0009801387786865234s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 4.410743713378906e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 1.33514404296875e-05s
INFO | --- Analysis for TP-data took 8.449575424194336s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.6082990169525146s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.30759572982788086s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.02558755874633789s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0013878345489501953s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 6.985664367675781e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for traditional-korean-medicine took 3.9354546070098877s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.25338315963745117s
Availability | VoID file availability check for Traffic Scotland took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.3562798500061035s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.02242255210876465s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 4.00543212890625e-05s
Believability | Calculation of trust value for Traffic Scotland took 1.0013580322265625e-05s
INFO | --- Analysis for traffic-scotland took 4.009395360946655s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.052852630615234375s
Availability | VoID file availability check for Transparency International Linked Data took 0.0007312297821044922s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.30991625785827637s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.02098393440246582s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00011301040649414062s
Believability | Calculation of trust value for Transparency International Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for transparency-linked-data took 3.0166175365448s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.6778182983398438s
Availability | VoID file availability check for transport.data.gov.uk took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.3036067485809326s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.021322250366210938s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.489059448242188e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 9.298324584960938e-06s
INFO | --- Analysis for transport-data-gov-uk took 4.395079135894775s
Availability | SPARQL endpoint availability check for OpenUpLabs Transport took 9.059906005859375e-05s
Availability | VoID file availability check for OpenUpLabs Transport took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for OpenUpLabs Transport took 0.40274620056152344s
Reputation | Calculation of the PageRank for OpenUpLabs Transport took 0.022443532943725586s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Transport took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Transport took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Transport took 3.4809112548828125e-05s
Believability | Calculation of trust value for OpenUpLabs Transport took 1.1682510375976562e-05s
INFO | --- Analysis for transport-openuplabs took 3.599461793899536s
Availability | SPARQL endpoint availability check for Trelios took 9.250640869140625e-05s
Availability | VoID file availability check for Trelios took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Trelios took 0.343738317489624s
Reputation | Calculation of the PageRank for Trelios took 0.02150130271911621s
Interlinking | Calculation of Degree of Connection for Trelios took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.3113021850585938e-05s
Believability | Calculation of trust value for Trelios took 1.2636184692382812e-05s
INFO | --- Analysis for Trelios took 2.923076868057251s
Availability | SPARQL endpoint availability check for Twarql took 10.636745691299438s
Availability | VoID file availability check for Twarql took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Twarql took 0.4851675033569336s
Reputation | Calculation of the PageRank for Twarql took 0.021164655685424805s
Interlinking | Calculation of Degree of Connection for Twarql took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Twarql took 7.081031799316406e-05s
Believability | Calculation of trust value for Twarql took 1.2636184692382812e-05s
INFO | --- Analysis for twarql took 13.754607439041138s
Availability | SPARQL endpoint availability check for TWC Data-gov took 6.580352783203125e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.34317779541015625s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.022061586380004883s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.600120544433594e-05s
Believability | Calculation of trust value for TWC Data-gov took 9.059906005859375e-06s
INFO | --- Analysis for twc-data-gov took 13.568929433822632s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.13988304138183594s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007190704345703125s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.34984564781188965s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.02107095718383789s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 3.9577484130859375e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 1.0251998901367188e-05s
INFO | --- Analysis for twc-healthdata took 15.954410076141357s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.59318995475769s
Availability | VoID file availability check for Instance Hub (all) took 0.0008344650268554688s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.35761308670043945s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.021887779235839844s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0008993148803710938s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 9.179115295410156e-05s
Believability | Calculation of trust value for Instance Hub (all) took 1.2636184692382812e-05s
INFO | --- Analysis for twc-hub took 76.82015872001648s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.12989306449890137s
Availability | VoID file availability check for IEEE VIS Source Data took 0.00034880638122558594s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.43806958198547363s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.028968095779418945s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0015513896942138672s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.0001704692840576172s
Believability | Calculation of trust value for IEEE VIS Source Data took 1.3113021850585938e-05s
INFO | --- Analysis for twc-ieeevis took 102.68914699554443s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 4.458427429199219e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.3698892593383789s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.021143674850463867s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 9.107589721679688e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 9.5367431640625e-06s
INFO | --- Analysis for twc-logd took 3.3255159854888916s
Availability | SPARQL endpoint availability check for twc-opendap took 0.11941218376159668s
Availability | VoID file availability check for twc-opendap took 0.00033855438232421875s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.3393819332122803s
Reputation | Calculation of the PageRank for twc-opendap took 0.022109270095825195s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 8.249282836914062e-05s
Believability | Calculation of trust value for twc-opendap took 8.106231689453125e-06s
INFO | --- Analysis for twc-opendap took 51.08230924606323s
Availability | SPARQL endpoint availability check for Twitter Linked Data Service took 8.344650268554688e-05s
Availability | VoID file availability check for Twitter Linked Data Service took 0.000293731689453125s
Completeness | Calculation of interlinking completeness for Twitter Linked Data Service took 0.300783634185791s
Reputation | Calculation of the PageRank for Twitter Linked Data Service took 0.021106481552124023s
Interlinking | Calculation of Degree of Connection for Twitter Linked Data Service took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Twitter Linked Data Service took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Twitter Linked Data Service took 3.409385681152344e-05s
Believability | Calculation of trust value for Twitter Linked Data Service took 8.106231689453125e-06s
INFO | --- Analysis for twitter-lids took 3.5649778842926025s
Availability | SPARQL endpoint availability check for typepad took 4.601478576660156e-05s
Availability | VoID file availability check for typepad took 0.0003895759582519531s
Completeness | Calculation of interlinking completeness for typepad took 0.6497185230255127s
Reputation | Calculation of the PageRank for typepad took 0.021048307418823242s
Interlinking | Calculation of Degree of Connection for typepad took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for typepad took 5.269050598144531e-05s
Believability | Calculation of trust value for typepad took 1.239776611328125e-05s
INFO | --- Analysis for typepad took 4.03436541557312s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.9710648059844971s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.3013927936553955s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.02112102508544922s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.696846008300781e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.239776611328125e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 5.829186916351318s
Availability | SPARQL endpoint availability check for Uberblic.org took 60.055726051330566s
Availability | VoID file availability check for Uberblic.org took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.42226481437683105s
Reputation | Calculation of the PageRank for Uberblic.org took 0.021200180053710938s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00011968612670898438s
Believability | Calculation of trust value for Uberblic.org took 1.239776611328125e-05s
INFO | --- Analysis for uberblic took 163.31816387176514s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.6655678749084473s
Availability | VoID file availability check for UDante in LiLa took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.521583080291748s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.021435022354125977s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 4.363059997558594e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for UDante took 5.081199645996094s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 1.033860206604004s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.2923581600189209s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.021309614181518555s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0008056163787841797s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 3.743171691894531e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 8.106231689453125e-06s
INFO | --- Analysis for ufo took 5.98163914680481s
Availability | SPARQL endpoint availability check for Uganda Disasters took 4.887580871582031e-05s
Availability | VoID file availability check for Uganda Disasters took 0.0004222393035888672s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.3585972785949707s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.02151799201965332s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 5.245208740234375e-05s
Believability | Calculation of trust value for Uganda Disasters took 1.2159347534179688e-05s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.987107038497925s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.06025195121765137s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0004031658172607422s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.32659316062927246s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.032001495361328125s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0011587142944335938s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.00012993812561035156s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for uis-linked-data took 3.3387691974639893s
Availability | SPARQL endpoint availability check for UK Legislation took 9.822845458984375e-05s
Availability | VoID file availability check for UK Legislation took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.3645288944244385s
Reputation | Calculation of the PageRank for UK Legislation took 0.021381616592407227s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 9.751319885253906e-05s
Believability | Calculation of trust value for UK Legislation took 9.5367431640625e-06s
INFO | --- Analysis for uk-legislation-api took 4.013523578643799s
Availability | SPARQL endpoint availability check for UK Postcodes took 4.8160552978515625e-05s
Availability | VoID file availability check for UK Postcodes took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.29987072944641113s
Reputation | Calculation of the PageRank for UK Postcodes took 0.02108311653137207s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 6.246566772460938e-05s
Believability | Calculation of trust value for UK Postcodes took 7.867813110351562e-06s
INFO | --- Analysis for uk-postcodes took 23.022493839263916s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 7.128715515136719e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.32287096977233887s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.02248239517211914s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.001474618911743164s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00016069412231445312s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 9.5367431640625e-06s
INFO | --- Analysis for umbel took 7.09782338142395s
Availability | SPARQL endpoint availability check for German environmental thesaurus UMTHES took 4.673004150390625e-05s
Availability | VoID file availability check for German environmental thesaurus UMTHES took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for German environmental thesaurus UMTHES took 0.32324910163879395s
Reputation | Calculation of the PageRank for German environmental thesaurus UMTHES took 0.022646427154541016s
Interlinking | Calculation of Degree of Connection for German environmental thesaurus UMTHES took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for German environmental thesaurus UMTHES took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for German environmental thesaurus UMTHES took 4.7206878662109375e-05s
Believability | Calculation of trust value for German environmental thesaurus UMTHES took 5.245208740234375e-06s
INFO | --- Analysis for umthes took 4.042094707489014s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 2.6558353900909424s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.000919342041015625s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.3664984703063965s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.022762537002563477s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0009300708770751953s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.838539123535156e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 6.198883056640625e-06s
INFO | --- Analysis for un-hazardous-numbers took 14.061887264251709s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.3392181396484375e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.29795002937316895s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.021185636520385742s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 5.745887756347656e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for unescothes took 3.744271993637085s
Availability | SPARQL endpoint availability check for UniProt took 3.7150402069091797s
Availability | VoID file availability check for UniProt took 0.0006899833679199219s
Extra | Recovery of all triples for UniProt took 18.470770359039307s
Performance | Total latancy measurement for UniProt took 7.112908601760864s
Amount of data | Number of triples check for UniProt took 0.5651352405548096s
Interoperability | New terms check for UniProt took 1.8917081356048584s
Versatility | Languages check for UniProt took 2.0758299827575684s
Interpretability | Number of blank nodes check for UniProt took 3.5235073566436768s
Interpretability | RDF structures check for UniProt took 1.6890263557434082s
Versatility | Serialization formats check for UniProt took 2.2608232498168945s
Availability | RDF dump link check for UniProt took 0.31222081184387207s
License | MR license check for UniProt took 1.218447208404541s
License | HR license check for UniProt took 300.14536714553833s
Amount of data | Number of property check for UniProt took 0.08324480056762695s
Understandability | Number of label check for UniProt took 53.67271709442139s
Understandability | URI regex check for UniProt took 0.9946191310882568s
Understandability | Vocabs check for UniProt took 0.7883591651916504s
Verifiability | Authors check for UniProt took 1.4224660396575928s
Verifiability | Publishers check for UniProt took 1.2036166191101074s
Performance | Throughput check for UniProt took 34.809293031692505s
Amount of data | Check the number of entities for UniProt took 7.605552673339844e-05s
Verifiability | Contribs. check for UniProt took 0.7675020694732666s
Interlinking | sameAs chians check for UniProt took 0.6246323585510254s
Interlinking | skos check for UniProt took 1.4126200675964355s
Interlinking | skos check for UniProt took 0.0902247428894043s
Timeliness | dataset update frequency check for UniProt took 1.349090576171875s
Currency | Creation date check for UniProt took 1.750650405883789s
Currency | Modification date check for UniProt took 1.5824759006500244s
Rep.Conc. | URIs length for UniProt took 118.37361240386963s
Interoperability | New vocabularies check for UniProt took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for UniProt took 0.4866943359375s
Accuracy | Check Functional Property for UniProt took 0.34412670135498047s
Accuracy | Check Inverse Functional Property for UniProt took 0.34270620346069336s
Accuracy | Check Empty annotation labels for UniProt took 11.000500440597534s
Accuracy | Check White space in annotation for UniProt took 2.5452752113342285s
Accuracy | Check Datatype consistency for UniProt took 7.420013427734375s
Consistency | Disjoint class check for UniProt took 0.34220314025878906s
Consistency | Check Misplaced properties for UniProt took 2.629021167755127s
Consistency | Check Ontology hijacking for UniProt took 9.227707386016846s
Consistency | Check Invalid usage of undefined classes for UniProt took 21590.296792030334s
Consistency | Check Invalid usage of undefined properties for UniProt took 2.1638710498809814s
Conciseness | Check Extensional conciseness for UniProt took 2.738241195678711s
Conciseness | Check Intensional conciseness for UniProt took 0.7418794631958008s
Security | Sign check for UniProt took 1.059190034866333s
Availability | Check URIs Dereferenciability for UniProt took 4.7009501457214355s
Completeness | Calculation of interlinking completeness for UniProt took 0.4471454620361328s
Reputation | Calculation of the PageRank for UniProt took 0.024294376373291016s
Interlinking | Calculation of Degree of Connection for UniProt took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for UniProt took 5.5789947509765625e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 2.1457672119140625e-06s
Believability | Calculation of trust value for UniProt took 1.1920928955078125e-05s
INFO | --- Analysis for UniProt took 22622.808738470078s
Availability | SPARQL endpoint availability check for UniProt took 3.5797789096832275s
Availability | VoID file availability check for UniProt took 0.0006973743438720703s
Extra | Recovery of all triples for UniProt took 17.957507848739624s
Performance | Total latancy measurement for UniProt took 8.250776290893555s
Amount of data | Number of triples check for UniProt took 0.6382846832275391s
Versatility | Languages check for UniProt took 2.048651933670044s
Interpretability | Number of blank nodes check for UniProt took 3.360884189605713s
Security | Check HTTPS for UniProt took 4.106562376022339s
Interpretability | RDF structures check for UniProt took 0.1869657039642334s
Versatility | Serialization formats check for UniProt took 0.1945357322692871s
Availability | RDF dump link check for UniProt took 0.5315172672271729s
License | MR license check for UniProt took 0.18699121475219727s
License | HR license check for UniProt took 0.18179917335510254s
Amount of data | Number of property check for UniProt took 0.20969891548156738s
Understandability | Number of label check for UniProt took 0.1997065544128418s
Understandability | URI regex check for UniProt took 0.3740880489349365s
Understandability | Vocabs check for UniProt took 0.17817115783691406s
Verifiability | Authors check for UniProt took 0.1685488224029541s
Verifiability | Publishers check for UniProt took 0.19084572792053223s
Performance | Throughput check for UniProt took 39.56991744041443s
Amount of data | Check the number of entities for UniProt took 0.00011563301086425781s
Verifiability | Contribs. check for UniProt took 0.2310500144958496s
Interlinking | sameAs chians check for UniProt took 0.19054961204528809s
Interlinking | skos check for UniProt took 0.17107343673706055s
Interlinking | skos check for UniProt took 0.14593195915222168s
Timeliness | dataset update frequency check for UniProt took 0.17976069450378418s
Currency | Creation date check for UniProt took 0.37608838081359863s
Currency | Modification date check for UniProt took 0.3486788272857666s
Rep.Conc. | URIs length for UniProt took 123.64399671554565s
Interoperability | New vocabularies check for UniProt took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for UniProt took 0.2314589023590088s
Accuracy | Check Datatype consistency for UniProt took 7.412062644958496s
Consistency | Disjoint class check for UniProt took 0.1845691204071045s
Consistency | Check Ontology hijacking for UniProt took 0.18267273902893066s
Consistency | Check Invalid usage of undefined properties for UniProt took 2.0044078826904297s
Conciseness | Check Extensional conciseness for UniProt took 2.8595516681671143s
Security | Sign check for UniProt took 0.18236613273620605s
Availability | Check URIs Dereferenciability for UniProt took 4.222536325454712s
Completeness | Calculation of interlinking completeness for UniProt took 0.5698366165161133s
Reputation | Calculation of the PageRank for UniProt took 0.022391557693481445s
Interlinking | Calculation of Degree of Connection for UniProt took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for UniProt took 6.270408630371094e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 7.152557373046875e-07s
Believability | Calculation of trust value for UniProt took 1.239776611328125e-05s
INFO | --- Analysis for uniprot took 769.7931816577911s
Availability | SPARQL endpoint availability check for UniProt citations took 0.00016164779663085938s
Availability | VoID file availability check for UniProt citations took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for UniProt citations took 0.30194830894470215s
Reputation | Calculation of the PageRank for UniProt citations took 0.022106647491455078s
Interlinking | Calculation of Degree of Connection for UniProt citations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UniProt citations took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for UniProt citations took 3.504753112792969e-05s
Believability | Calculation of trust value for UniProt citations took 1.1920928955078125e-05s
INFO | --- Analysis for uniprot-citations took 3.854435682296753s
Availability | SPARQL endpoint availability check for UniProt databases took 8.7738037109375e-05s
Availability | VoID file availability check for UniProt databases took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for UniProt databases took 0.313570499420166s
Reputation | Calculation of the PageRank for UniProt databases took 0.023148536682128906s
Interlinking | Calculation of Degree of Connection for UniProt databases took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UniProt databases took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for UniProt databases took 3.695487976074219e-05s
Believability | Calculation of trust value for UniProt databases took 1.2874603271484375e-05s
INFO | --- Analysis for uniprot-databases took 3.5530197620391846s
Availability | SPARQL endpoint availability check for uniprot-metadata took 9.775161743164062e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0008082389831542969s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.2825798988342285s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.021179914474487305s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.961822509765625e-05s
Believability | Calculation of trust value for uniprot-metadata took 8.106231689453125e-06s
INFO | --- Analysis for uniprot-metadata took 4.171140909194946s
Availability | SPARQL endpoint availability check for UniProt UniParc took 4.2438507080078125e-05s
Availability | VoID file availability check for UniProt UniParc took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for UniProt UniParc took 0.3028585910797119s
Reputation | Calculation of the PageRank for UniProt UniParc took 0.020757198333740234s
Interlinking | Calculation of Degree of Connection for UniProt UniParc took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for UniProt UniParc took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for UniProt UniParc took 3.504753112792969e-05s
Believability | Calculation of trust value for UniProt UniParc took 1.3589859008789062e-05s
INFO | --- Analysis for uniprot-uniparc took 3.718595504760742s
Availability | SPARQL endpoint availability check for UniProt UniPathway took 8.797645568847656e-05s
Availability | VoID file availability check for UniProt UniPathway took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for UniProt UniPathway took 0.3146798610687256s
Reputation | Calculation of the PageRank for UniProt UniPathway took 0.021055936813354492s
Interlinking | Calculation of Degree of Connection for UniProt UniPathway took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for UniProt UniPathway took 0.000812530517578125s
Interlinking | Calculation of Clustering coefficient for UniProt UniPathway took 4.124641418457031e-05s
Believability | Calculation of trust value for UniProt UniPathway took 1.239776611328125e-05s
INFO | --- Analysis for uniprot-unipathway took 3.5279977321624756s
Availability | SPARQL endpoint availability check for UniProtKB took 3.4675469398498535s
Availability | VoID file availability check for UniProtKB took 0.000545501708984375s
Extra | Recovery of all triples for UniProtKB took 16.51684069633484s
Performance | Total latancy measurement for UniProtKB took 7.479163408279419s
Amount of data | Number of triples check for UniProtKB took 0.4419112205505371s
Interoperability | New terms check for UniProtKB took 1.906844139099121s
Versatility | Languages check for UniProtKB took 1.6506552696228027s
Interpretability | Number of blank nodes check for UniProtKB took 3.325561761856079s
Interpretability | RDF structures check for UniProtKB took 1.6244289875030518s
Versatility | Serialization formats check for UniProtKB took 2.201157808303833s
Availability | RDF dump link check for UniProtKB took 0.32059311866760254s
License | MR license check for UniProtKB took 1.2163095474243164s
License | HR license check for UniProtKB took 300.1617681980133s
Amount of data | Number of property check for UniProtKB took 0.1577162742614746s
Understandability | Number of label check for UniProtKB took 57.84879422187805s
Understandability | URI regex check for UniProtKB took 0.9042093753814697s
Understandability | Vocabs check for UniProtKB took 0.9920156002044678s
Verifiability | Authors check for UniProtKB took 1.402224063873291s
Verifiability | Publishers check for UniProtKB took 1.1957130432128906s
Performance | Throughput check for UniProtKB took 36.862807512283325s
Amount of data | Check the number of entities for UniProtKB took 0.00011897087097167969s
Verifiability | Contribs. check for UniProtKB took 0.7960894107818604s
Interlinking | sameAs chians check for UniProtKB took 0.644258975982666s
Interlinking | skos check for UniProtKB took 1.361311674118042s
Interlinking | skos check for UniProtKB took 0.08842706680297852s
Timeliness | dataset update frequency check for UniProtKB took 1.4190289974212646s
Currency | Creation date check for UniProtKB took 1.822768211364746s
Currency | Modification date check for UniProtKB took 1.6937017440795898s
Rep.Conc. | URIs length for UniProtKB took 118.37627077102661s
Interoperability | New vocabularies check for UniProtKB took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.3792998790740967s
Accuracy | Check Functional Property for UniProtKB took 0.3500330448150635s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.33606696128845215s
Accuracy | Check Empty annotation labels for UniProtKB took 11.429351568222046s
Accuracy | Check White space in annotation for UniProtKB took 2.5092718601226807s
Accuracy | Check Datatype consistency for UniProtKB took 7.459640026092529s
Consistency | Disjoint class check for UniProtKB took 0.4044358730316162s
Consistency | Check Misplaced properties for UniProtKB took 2.48775577545166s
Consistency | Check Ontology hijacking for UniProtKB took 7.729060173034668s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 23040.432025671005s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 2.0971908569335938s
Conciseness | Check Extensional conciseness for UniProtKB took 2.7224695682525635s
Conciseness | Check Intensional conciseness for UniProtKB took 0.9648923873901367s
Security | Sign check for UniProtKB took 1.5190787315368652s
Availability | Check URIs Dereferenciability for UniProtKB took 4.625859022140503s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.6458840370178223s
Reputation | Calculation of the PageRank for UniProtKB took 0.022593021392822266s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 7.414817810058594e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 2.1457672119140625e-06s
Believability | Calculation of trust value for UniProtKB took 1.239776611328125e-05s
INFO | --- Analysis for uniprotkb took 24073.188019275665s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 8.940696716308594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.32225871086120605s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.021215200424194336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 13.869183540344238s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.553794860839844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.000415802001953125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.29677414894104004s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.021295785903930664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.601478576660156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 4.65958046913147s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 8.845329284667969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0007379055023193359s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.31923723220825195s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.021242856979370117s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 1.6927719116210938e-05s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.906389951705933s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.649162292480469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.30655384063720703s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.021015644073486328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.886120796203613s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.32783031463623047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.021004676818847656s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 13.927763223648071s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 9.512901306152344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0007271766662597656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.3432319164276123s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.021330833435058594s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 13.893312931060791s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0007660388946533203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.28536343574523926s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.021256685256958008s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 4.36584734916687s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 0.00011229515075683594s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0007140636444091797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.3098428249359131s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.021205902099609375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.763380765914917s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 9.250640869140625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.32708239555358887s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.02220749855041504s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0008528232574462891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.6253204345703125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.775280952453613s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 9.059906005859375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.3168957233428955s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.021216869354248047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.853751182556152s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 5.793571472167969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0008366107940673828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.39867424964904785s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.02318882942199707s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 4.57763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 13.590687274932861s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 9.298324584960938e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.3111593723297119s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.021142005920410156s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.649162292480469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 13.772783756256104s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 9.703636169433594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.3398702144622803s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.021375179290771484s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-danish took 4.50940203666687s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 6.914138793945312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.29659271240234375s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.02119302749633789s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.671919345855713s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.00010800361633300781s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0007810592651367188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.3848435878753662s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.02416706085205078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.696846008300781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 13.580901861190796s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0007526874542236328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.36969685554504395s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.021371126174926758s
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.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-english took 13.617766380310059s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 8.797645568847656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0007333755493164062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.39005208015441895s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.021149635314941406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.572073936462402s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 9.179115295410156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.3524026870727539s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.020983457565307617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.696846008300781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 13.556570053100586s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.3507814407348633s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.021226882934570312s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 13.796946287155151s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0003871917724609375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.29311513900756836s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.02160024642944336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 3.409385681152344e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.649162292480469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 5.056962251663208s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 8.654594421386719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.3527870178222656s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.021143674850463867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 4.863739013671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 3.528594970703125e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 13.743242502212524s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 8.797645568847656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0007131099700927734s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.2885730266571045s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.0210726261138916s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0008041858673095703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.649162292480469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.658823728561401s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 9.1552734375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0009264945983886719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.2779996395111084s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.021940946578979492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 4.935264587402344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.59062933921814s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 4.696846008300781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.2954392433166504s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.02261829376220703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 4.489403247833252s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 7.486343383789062e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.35857677459716797s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.020971059799194336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-german took 4.807685136795044s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 4.601478576660156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.00041103363037109375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.2951638698577881s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.02243494987487793s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.601478576660156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 4.543643951416016s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 4.76837158203125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.263568639755249s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.02135324478149414s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 4.3392181396484375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-greek took 4.1799092292785645s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 9.107589721679688e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0007348060607910156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.30499863624572754s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.022249698638916016s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.699641227722168s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 4.76837158203125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0007419586181640625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.3401007652282715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.02091383934020996s
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.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 4.3392181396484375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.716125249862671s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 9.274482727050781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.3313469886779785s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.021112680435180664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 4.715938091278076s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 5.888938903808594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.3135721683502197s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.022684335708618164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0009071826934814453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 5.507469177246094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.697818517684937s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 8.58306884765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.3104398250579834s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.021221637725830078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0008089542388916016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-irish took 4.441003799438477s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 9.107589721679688e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0007572174072265625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.5782558917999268s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.02099132537841797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-italian took 14.12074875831604s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 9.107589721679688e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0007469654083251953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.32605576515197754s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.021023035049438477s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.651458978652954s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 9.655952453613281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.3356292247772217s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.021691322326660156s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 4.601478576660156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 4.61165714263916s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 8.96453857421875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0008053779602050781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.30394935607910156s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.02129960060119629s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 5.364418029785156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 13.73129940032959s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 0.00017070770263671875s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0007262229919433594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.47072601318359375s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.02114129066467285s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin took 4.822809934616089s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.5326826572418213s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.021341562271118164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 4.887580871582031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 13.713640451431274s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0006461143493652344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.29923057556152344s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.021485090255737305s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 5.078315734863281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 8.821487426757812e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 13.579994201660156s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 5.030632019042969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.34621238708496094s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.036827802658081055s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0008492469787597656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 6.0558319091796875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.630178213119507s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 8.726119995117188e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0008144378662109375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.3594076633453369s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.021291494369506836s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 5.1021575927734375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 13.641986608505249s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0001373291015625s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.31339335441589355s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.021607398986816406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0008728504180908203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 5.14984130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.618292093276978s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 8.535385131835938e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0007078647613525391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.338026762008667s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.021567583084106445s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.839897155761719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-persian took 4.679532289505005s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 0.00012421607971191406s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.29703736305236816s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.022284984588623047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.701646327972412s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 6.198883056640625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.37851691246032715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.021028518676757812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 4.57763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 13.32349419593811s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.57763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0008122920989990234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.3530151844024658s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.02132725715637207s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.9591064453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 13.548572063446045s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 7.128715515136719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.31895971298217773s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.022819995880126953s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0008051395416259766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 4.7206878662109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 13.580374479293823s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0007677078247070312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.3401510715484619s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.021085739135742188s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.74019479751587s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 9.202957153320312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.3245391845703125s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.023303747177124023s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 5.054473876953125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.785284519195557s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 9.012222290039062e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.33034420013427734s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.02100229263305664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 4.379634380340576s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.000766754150390625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.47345662117004395s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.02112293243408203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 5.53131103515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.742775678634644s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 9.250640869140625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0007367134094238281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.4713454246520996s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.021371126174926758s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 4.601478576660156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 14.11521601676941s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 8.869171142578125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.33837127685546875s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.021345853805541992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 4.7206878662109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.857122421264648s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 9.036064147949219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.4881784915924072s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.021437883377075195s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 4.7206878662109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 14.348156213760376s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 9.369850158691406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.31362342834472656s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.02170562744140625s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0008296966552734375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 5.1021575927734375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 13.745007514953613s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 8.726119995117188e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.33446192741394043s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.021356821060180664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0008101463317871094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 4.935264587402344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 13.420190811157227s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 8.749961853027344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0008740425109863281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.28696680068969727s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.024611473083496094s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 4.7206878662109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 4.554200887680054s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 9.107589721679688e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.29578423500061035s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.0213778018951416s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 4.668056011199951s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007233619689941406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.3139686584472656s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.022783517837524414s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0008411407470703125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.9591064453125e-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 13.840080499649048s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 8.559226989746094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.3474390506744385s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.021160125732421875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.789099931716919s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 9.202957153320312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0008425712585449219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.299605131149292s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.02108025550842285s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 2.9325485229492188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 1.5735626220703125e-05s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.953809022903442s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 0.00010323524475097656s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0007276535034179688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.3026721477508545s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.022696733474731445s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0010690689086914062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 5.555152893066406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 13.567816972732544s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.000732421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.3593020439147949s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.02099323272705078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 14.032214403152466s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0007810592651367188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.5567960739135742s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.022211313247680664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.649162292480469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 14.077056646347046s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 8.749961853027344e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.3289921283721924s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.02096843719482422s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 7.152557373046875e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 1.1205673217773438e-05s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 4.349975347518921s
Availability | SPARQL endpoint availability check for Universitat Pompeu Fabra - linked data took 8.893013000488281e-05s
Availability | VoID file availability check for Universitat Pompeu Fabra - linked data took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for Universitat Pompeu Fabra - linked data took 0.3283355236053467s
Reputation | Calculation of the PageRank for Universitat Pompeu Fabra - linked data took 0.022463083267211914s
Interlinking | Calculation of Degree of Connection for Universitat Pompeu Fabra - linked data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universitat Pompeu Fabra - linked data took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Universitat Pompeu Fabra - linked data took 3.695487976074219e-05s
Believability | Calculation of trust value for Universitat Pompeu Fabra - linked data took 1.3113021850585938e-05s
INFO | --- Analysis for universitat-pompeu-fabra-linked-data took 3.584639072418213s
Availability | SPARQL endpoint availability check for University of Bristol took 8.511543273925781e-05s
Availability | VoID file availability check for University of Bristol took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for University of Bristol took 0.3404428958892822s
Reputation | Calculation of the PageRank for University of Bristol took 0.021228551864624023s
Interlinking | Calculation of Degree of Connection for University of Bristol took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for University of Bristol took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for University of Bristol took 3.409385681152344e-05s
Believability | Calculation of trust value for University of Bristol took 1.2159347534179688e-05s
INFO | --- Analysis for university-of-bristol took 3.441775321960449s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 9.059906005859375e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.3415212631225586s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.021025896072387695s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 5.555152893066406e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.1682510375976562e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 3.8666152954101562s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 4.506111145019531e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.4038729667663574s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.021308183670043945s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.910064697265625e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 1.5497207641601562e-05s
INFO | --- Analysis for university-sussex-reading-lists took 3.4099395275115967s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 8.218989610671997s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.3609461784362793s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.02110004425048828s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 7.605552673339844e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 8.106231689453125e-06s
INFO | --- Analysis for unodc took 21.24357795715332s
Availability | SPARQL endpoint availability check for Super Ontology took 0.00010561943054199219s
Availability | VoID file availability check for Super Ontology took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.3048088550567627s
Reputation | Calculation of the PageRank for Super Ontology took 0.021137714385986328s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 8.440017700195312e-05s
Believability | Calculation of trust value for Super Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for upper-ontology took 3.899770736694336s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 0.8985536098480225s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.3020358085632324s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.02130722999572754s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0008199214935302734s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.8623809814453125e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for Upper_Ontology took 4.713957071304321s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 4.553794860839844e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.3092374801635742s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.02147817611694336s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 3.7670135498046875e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 1.3113021850585938e-05s
INFO | --- Analysis for Urban_Atlas_ took 2.8565900325775146s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 0.19687438011169434s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.00032448768615722656s
Extra | Recovery of all triples for Urban Atlas dataset @PSNC took 117.79245090484619s
Performance | Total latancy measurement for Urban Atlas dataset @PSNC took 0.9791603088378906s
Amount of data | Number of triples check for Urban Atlas dataset @PSNC took 9.089815855026245s
Interoperability | New terms check for Urban Atlas dataset @PSNC took 14.233681201934814s
Versatility | Languages check for Urban Atlas dataset @PSNC took 300.21693873405457s
Interpretability | Number of blank nodes check for Urban Atlas dataset @PSNC took 2.1317975521087646s
Interpretability | RDF structures check for Urban Atlas dataset @PSNC took 0.2915492057800293s
Versatility | Serialization formats check for Urban Atlas dataset @PSNC took 7.383193016052246s
Availability | RDF dump link check for Urban Atlas dataset @PSNC took 0.24935030937194824s
License | MR license check for Urban Atlas dataset @PSNC took 0.6215100288391113s
License | HR license check for Urban Atlas dataset @PSNC took 300.20268416404724s
Amount of data | Number of property check for Urban Atlas dataset @PSNC took 0.21889019012451172s
Understandability | Number of label check for Urban Atlas dataset @PSNC took 2.874683380126953s
Understandability | URI regex check for Urban Atlas dataset @PSNC took 0.9375989437103271s
Understandability | Vocabs check for Urban Atlas dataset @PSNC took 0.5700812339782715s
Verifiability | Authors check for Urban Atlas dataset @PSNC took 0.2014157772064209s
Verifiability | Publishers check for Urban Atlas dataset @PSNC took 0.2692997455596924s
Performance | Throughput check for Urban Atlas dataset @PSNC took 11.195409536361694s
Amount of data | Check the number of entities for Urban Atlas dataset @PSNC took 9.608268737792969e-05s
Verifiability | Contribs. check for Urban Atlas dataset @PSNC took 0.2142961025238037s
Interlinking | sameAs chians check for Urban Atlas dataset @PSNC took 0.18720293045043945s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.427060604095459s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.3988521099090576s
Timeliness | dataset update frequency check for Urban Atlas dataset @PSNC took 5.599608898162842s
Currency | Creation date check for Urban Atlas dataset @PSNC took 0.47614026069641113s
Currency | Modification date check for Urban Atlas dataset @PSNC took 0.22071242332458496s
Rep.Conc. | URIs length for Urban Atlas dataset @PSNC took 153.7943353652954s
Interoperability | New vocabularies check for Urban Atlas dataset @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Urban Atlas dataset @PSNC took 0.19780850410461426s
Accuracy | Check Functional Property for Urban Atlas dataset @PSNC took 0.4621889591217041s
Accuracy | Check Inverse Functional Property for Urban Atlas dataset @PSNC took 0.4611232280731201s
Accuracy | Check Empty annotation labels for Urban Atlas dataset @PSNC took 45.209020376205444s
Accuracy | Check White space in annotation for Urban Atlas dataset @PSNC took 2.7352802753448486s
Accuracy | Check Datatype consistency for Urban Atlas dataset @PSNC took 2.73356294631958s
Consistency | Disjoint class check for Urban Atlas dataset @PSNC took 0.18381452560424805s
Consistency | Check Misplaced properties for Urban Atlas dataset @PSNC took 85.79992151260376s
Consistency | Misplaced classes for Urban Atlas dataset @PSNC took 8.516355991363525s
Consistency | Check Ontology hijacking for Urban Atlas dataset @PSNC took 41.12645101547241s
Consistency | Check Invalid usage of undefined classes for Urban Atlas dataset @PSNC took 1.541851282119751s
Consistency | Check Invalid usage of undefined properties for Urban Atlas dataset @PSNC took 87.26254034042358s
Conciseness | Check Extensional conciseness for Urban Atlas dataset @PSNC took 2.7800827026367188s
Conciseness | Check Intensional conciseness for Urban Atlas dataset @PSNC took 0.6306483745574951s
Security | Sign check for Urban Atlas dataset @PSNC took 1.2645270824432373s
Availability | Check URIs Dereferenciability for Urban Atlas dataset @PSNC took 10.29140853881836s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.6513307094573975s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.022589683532714844s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0011172294616699219s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 5.626678466796875e-05s
Interoperability | Check the re-using of existing vocabs for Urban Atlas dataset @PSNC took 3.5762786865234375e-06s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 1.33514404296875e-05s
INFO | --- Analysis for Urban_Atlas_Dataset took 3107.0320518016815s
Availability | SPARQL endpoint availability check for URIBurner took 1.0111327171325684s
Availability | VoID file availability check for URIBurner took 0.000621795654296875s
Extra | Recovery of all triples for URIBurner took 122.25194048881531s
Performance | Total latancy measurement for URIBurner took 2.7439725399017334s
Amount of data | Number of triples check for URIBurner took 3.5000717639923096s
Interoperability | New terms check for URIBurner took 37.47772145271301s
Versatility | Languages check for URIBurner took 122.64415621757507s
Interpretability | Number of blank nodes check for URIBurner took 1.8610904216766357s
Security | Check HTTPS for URIBurner took 0.9260025024414062s
Interpretability | RDF structures check for URIBurner took 2.3216962814331055s
Versatility | Serialization formats check for URIBurner took 6.607300043106079s
Availability | RDF dump link check for URIBurner took 45.56455683708191s
License | MR license check for URIBurner took 1.3195688724517822s
License | HR license check for URIBurner took 122.73769760131836s
Amount of data | Number of property check for URIBurner took 0.7633588314056396s
Understandability | Number of label check for URIBurner took 3.3909575939178467s
Understandability | URI regex check for URIBurner took 1.3021681308746338s
Understandability | Vocabs check for URIBurner took 0.6403868198394775s
Verifiability | Authors check for URIBurner took 0.7703042030334473s
Verifiability | Publishers check for URIBurner took 0.6122605800628662s
Performance | Throughput check for URIBurner took 11.12834906578064s
Amount of data | Check the number of entities for URIBurner took 9.1552734375e-05s
Verifiability | Contribs. check for URIBurner took 0.643345832824707s
Interlinking | sameAs chians check for URIBurner took 0.9759747982025146s
Interlinking | skos check for URIBurner took 0.8196167945861816s
Interlinking | skos check for URIBurner took 0.532512903213501s
Timeliness | dataset update frequency check for URIBurner took 1.0732238292694092s
Currency | Creation date check for URIBurner took 3.1642849445343018s
Currency | Modification date check for URIBurner took 0.7698206901550293s
Rep.Conc. | URIs length for URIBurner took 114.13632488250732s
Interoperability | New vocabularies check for URIBurner took 35.49961185455322s
Consistency | Deprecated classes/propertiers check for URIBurner took 0.617358922958374s
Accuracy | Check Functional Property for URIBurner took 0.6030187606811523s
Accuracy | Check Inverse Functional Property for URIBurner took 0.566835880279541s
Accuracy | Check Empty annotation labels for URIBurner took 55.35839223861694s
Accuracy | Check White space in annotation for URIBurner took 0.19149398803710938s
Consistency | Disjoint class check for URIBurner took 0.6006796360015869s
Consistency | Check Misplaced properties for URIBurner took 430.46069502830505s
Consistency | Misplaced classes for URIBurner took 59.9778892993927s
Consistency | Check Ontology hijacking for URIBurner took 66.74166917800903s
Consistency | Check Invalid usage of undefined properties for URIBurner took 65.0891535282135s
Conciseness | Check Extensional conciseness for URIBurner took 0.0001685619354248047s
Conciseness | Check Intensional conciseness for URIBurner took 108.5660240650177s
Security | Sign check for URIBurner took 0.7829585075378418s
Completeness | Calculation of interlinking completeness for URIBurner took 0.3756582736968994s
Reputation | Calculation of the PageRank for URIBurner took 0.02260279655456543s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for URIBurner took 0.00011372566223144531s
Interoperability | Check the re-using of existing vocabs for URIBurner took 145.02880811691284s
Believability | Calculation of trust value for URIBurner took 1.2636184692382812e-05s
INFO | --- Analysis for uriburner took 11416.804168701172s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00011205673217773438s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.2936728000640869s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02121424674987793s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.361701965332031e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.1920928955078125e-05s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 2.8719639778137207s
Availability | SPARQL endpoint availability check for Legija Stranaca took 4.4345855712890625e-05s
Availability | VoID file availability check for Legija Stranaca took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.28574585914611816s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.02103114128112793s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 3.4332275390625e-05s
Believability | Calculation of trust value for Legija Stranaca took 1.2159347534179688e-05s
INFO | --- Analysis for Uros_Legija_Susa took 2.906686544418335s
Availability | SPARQL endpoint availability check for Legija took 0.00010561943054199219s
Availability | VoID file availability check for Legija took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Legija took 0.30875515937805176s
Reputation | Calculation of the PageRank for Legija took 0.02084827423095703s
Interlinking | Calculation of Degree of Connection for Legija took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Legija took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Legija took 3.814697265625e-05s
Believability | Calculation of trust value for Legija took 1.1444091796875e-05s
INFO | --- Analysis for Uros_Susa took 2.9121835231781006s
Availability | SPARQL endpoint availability check for USAGE review corpus took 26.501044750213623s
Availability | VoID file availability check for USAGE review corpus took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.32648277282714844s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.021177053451538086s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.457069396972656e-05s
Believability | Calculation of trust value for USAGE review corpus took 1.0728836059570312e-05s
INFO | --- Analysis for usage-review-corpus took 91.80141496658325s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 4.163144111633301s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.3363609313964844s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.022077322006225586s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.987022399902344e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 1.3828277587890625e-05s
INFO | --- Analysis for utpl-lod took 11.150655269622803s
Availability | SPARQL endpoint availability check for Výkazy zisku a ztrát obcí ČR took 4.363059997558594e-05s
Availability | VoID file availability check for Výkazy zisku a ztrát obcí ČR took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Výkazy zisku a ztrát obcí ČR took 0.36704421043395996s
Reputation | Calculation of the PageRank for Výkazy zisku a ztrát obcí ČR took 0.021142959594726562s
Interlinking | Calculation of Degree of Connection for Výkazy zisku a ztrát obcí ČR took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Výkazy zisku a ztrát obcí ČR took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Výkazy zisku a ztrát obcí ČR took 3.528594970703125e-05s
Believability | Calculation of trust value for Výkazy zisku a ztrát obcí ČR took 1.2636184692382812e-05s
INFO | --- Analysis for v-kazy-zisku-a-ztr-t-obc---r took 3.7499887943267822s
Availability | SPARQL endpoint availability check for terrorist attack took 9.369850158691406e-05s
Availability | VoID file availability check for terrorist attack took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.3369591236114502s
Reputation | Calculation of the PageRank for terrorist attack took 0.021087169647216797s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 3.4332275390625e-05s
Believability | Calculation of trust value for terrorist attack took 1.239776611328125e-05s
INFO | --- Analysis for varsha took 4.89087986946106s
Availability | SPARQL endpoint availability check for VA took 8.893013000488281e-05s
Availability | VoID file availability check for VA took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for VA took 0.3128480911254883s
Reputation | Calculation of the PageRank for VA took 0.020836353302001953s
Interlinking | Calculation of Degree of Connection for VA took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VA took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for VA took 3.170967102050781e-05s
Believability | Calculation of trust value for VA took 1.049041748046875e-05s
INFO | --- Analysis for Vehicule_Autonome took 3.108443021774292s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 0.5800631046295166s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.3149418830871582s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.021664857864379883s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 4.029273986816406e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for VelezIndexTotiusArtis took 4.571158409118652s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 6.247161149978638s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.00036263465881347656s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.316403865814209s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.02103877067565918s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 9.226799011230469e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 1.3589859008789062e-05s
INFO | --- Analysis for verrijktkoninkrijk took 20.134236574172974s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 9.083747863769531e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.31763625144958496s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.021230697631835938s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00018167495727539062s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.3589859008789062e-05s
INFO | --- Analysis for viaf took 21.473072290420532s
Availability | SPARQL endpoint availability check for Vías Públicas de Zaragoza (Localización) took 4.2438507080078125e-05s
Availability | VoID file availability check for Vías Públicas de Zaragoza (Localización) took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Vías Públicas de Zaragoza (Localización) took 0.3243978023529053s
Reputation | Calculation of the PageRank for Vías Públicas de Zaragoza (Localización) took 0.021067380905151367s
Interlinking | Calculation of Degree of Connection for Vías Públicas de Zaragoza (Localización) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Vías Públicas de Zaragoza (Localización) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Vías Públicas de Zaragoza (Localización) took 3.3855438232421875e-05s
Believability | Calculation of trust value for Vías Públicas de Zaragoza (Localización) took 9.059906005859375e-06s
INFO | --- Analysis for vias-publicas-zaragoza took 4.028813123703003s
Availability | SPARQL endpoint availability check for Vihar Exports took 4.410743713378906e-05s
Availability | VoID file availability check for Vihar Exports took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.3348562717437744s
Reputation | Calculation of the PageRank for Vihar Exports took 0.021250009536743164s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 3.4332275390625e-05s
Believability | Calculation of trust value for Vihar Exports took 7.3909759521484375e-06s
INFO | --- Analysis for Vihar_Exports took 3.024639129638672s
Availability | SPARQL endpoint availability check for VIVO took 8.678436279296875e-05s
Availability | VoID file availability check for VIVO took 0.0007426738739013672s
Completeness | Calculation of interlinking completeness for VIVO took 0.3285353183746338s
Reputation | Calculation of the PageRank for VIVO took 0.021220922470092773s
Interlinking | Calculation of Degree of Connection for VIVO took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for VIVO took 7.462501525878906e-05s
Believability | Calculation of trust value for VIVO took 1.4066696166992188e-05s
INFO | --- Analysis for vivo took 5.489741325378418s
Availability | SPARQL endpoint availability check for VIVO Cornell took 9.179115295410156e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.3733329772949219s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.021136760711669922s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 9.226799011230469e-05s
Believability | Calculation of trust value for VIVO Cornell took 1.239776611328125e-05s
INFO | --- Analysis for vivo-cornell-university took 6.523747682571411s
Availability | SPARQL endpoint availability check for VIVO CU-Boulder took 8.58306884765625e-05s
Availability | VoID file availability check for VIVO CU-Boulder took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for VIVO CU-Boulder took 0.4823181629180908s
Reputation | Calculation of the PageRank for VIVO CU-Boulder took 0.022990703582763672s
Interlinking | Calculation of Degree of Connection for VIVO CU-Boulder took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO CU-Boulder took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for VIVO CU-Boulder took 3.314018249511719e-05s
Believability | Calculation of trust value for VIVO CU-Boulder took 1.1682510375976562e-05s
INFO | --- Analysis for vivo-cu-boulder took 3.9903345108032227s
Availability | SPARQL endpoint availability check for VIVO Indiana took 4.363059997558594e-05s
Availability | VoID file availability check for VIVO Indiana took 0.000579833984375s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.3459455966949463s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.020944595336914062s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 8.869171142578125e-05s
Believability | Calculation of trust value for VIVO Indiana took 1.1682510375976562e-05s
INFO | --- Analysis for vivo-indiana-university took 4.113320350646973s
Availability | SPARQL endpoint availability check for VIVO Ponce took 0.00012731552124023438s
Availability | VoID file availability check for VIVO Ponce took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.3663194179534912s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.0209958553314209s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.528594970703125e-05s
Believability | Calculation of trust value for VIVO Ponce took 8.58306884765625e-06s
INFO | --- Analysis for vivo-ponce took 3.545653820037842s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 4.363059997558594e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.3353288173675537s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.021572351455688477s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 4.172325134277344e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 8.106231689453125e-06s
INFO | --- Analysis for vivo-scripps-research-institute took 3.8662993907928467s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 0.0001316070556640625s
Availability | VoID file availability check for VIVO University of Florida took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.6435947418212891s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.02103590965270996s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 0.00010180473327636719s
Believability | Calculation of trust value for VIVO University of Florida took 1.1444091796875e-05s
INFO | --- Analysis for vivo-university-of-florida took 3.486171007156372s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 4.38690185546875e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.3142735958099365s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.02096724510192871s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 4.100799560546875e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 6.4373016357421875e-06s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 3.5472474098205566s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 4.9591064453125e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0007724761962890625s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.7811040878295898s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.021178007125854492s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 4.029273986816406e-05s
Believability | Calculation of trust value for VIVO WUSTL took 1.1682510375976562e-05s
INFO | --- Analysis for vivo-wustl took 4.0707762241363525s
Availability | SPARQL endpoint availability check for vivo2doi took 8.916854858398438e-05s
Availability | VoID file availability check for vivo2doi took 0.0006103515625s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.31436634063720703s
Reputation | Calculation of the PageRank for vivo2doi took 0.021052122116088867s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.482269287109375e-05s
Believability | Calculation of trust value for vivo2doi took 1.2159347534179688e-05s
INFO | --- Analysis for vivo2doi took 41.776407957077026s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 0.00010943412780761719s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.3330981731414795s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.0212709903717041s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 8.392333984375e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 1.1920928955078125e-05s
INFO | --- Analysis for vu-wordnet took 25.008405208587646s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.08223533630371094s
Availability | VoID file availability check for vulnerapedia took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.3156769275665283s
Reputation | Calculation of the PageRank for vulnerapedia took 0.020934104919433594s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0008003711700439453s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 7.43865966796875e-05s
Believability | Calculation of trust value for vulnerapedia took 1.2636184692382812e-05s
INFO | --- Analysis for vulnerapedia took 3.625988721847534s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 8.797645568847656e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.3278493881225586s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.022603511810302734s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.2874603271484375e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.1682510375976562e-05s
INFO | --- Analysis for VVASIAK took 2.8867709636688232s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 9.226799011230469e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.3033878803253174s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.020913362503051758s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.2901763916015625e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 1.3113021850585938e-05s
INFO | --- Analysis for Vyvasta took 3.2156105041503906s
Availability | SPARQL endpoint availability check for W3C took 9.822845458984375e-05s
Availability | VoID file availability check for W3C took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for W3C took 0.4809684753417969s
Reputation | Calculation of the PageRank for W3C took 0.021216869354248047s
Interlinking | Calculation of Degree of Connection for W3C took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for W3C took 0.0001475811004638672s
Believability | Calculation of trust value for W3C took 1.2159347534179688e-05s
INFO | --- Analysis for w3c took 3.736980438232422s
Availability | SPARQL endpoint availability check for W3C Provenance Incubator Group Vocabulary Mappings took 4.267692565917969e-05s
Availability | VoID file availability check for W3C Provenance Incubator Group Vocabulary Mappings took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for W3C Provenance Incubator Group Vocabulary Mappings took 0.34076476097106934s
Reputation | Calculation of the PageRank for W3C Provenance Incubator Group Vocabulary Mappings took 0.021330595016479492s
Interlinking | Calculation of Degree of Connection for W3C Provenance Incubator Group Vocabulary Mappings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for W3C Provenance Incubator Group Vocabulary Mappings took 0.000812530517578125s
Interlinking | Calculation of Clustering coefficient for W3C Provenance Incubator Group Vocabulary Mappings took 3.6716461181640625e-05s
Believability | Calculation of trust value for W3C Provenance Incubator Group Vocabulary Mappings took 1.2874603271484375e-05s
INFO | --- Analysis for w3c-provenance-incubator-group-vocabulary-mappings took 3.9669978618621826s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 0.00010466575622558594s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.36343908309936523s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.021500110626220703s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.0001201629638671875s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 1.2159347534179688e-05s
INFO | --- Analysis for w3c-wordnet took 3.9802286624908447s
Availability | SPARQL endpoint availability check for WarSampo took 0.36098742485046387s
Availability | VoID file availability check for WarSampo took 0.0007305145263671875s
Extra | Recovery of all triples for WarSampo took 23.6608464717865s
Performance | Total latancy measurement for WarSampo took 0.8599088191986084s
Amount of data | Number of triples check for WarSampo took 18.57572889328003s
Interoperability | New terms check for WarSampo took 3.8666112422943115s
Versatility | Languages check for WarSampo took 60.21677207946777s
Interpretability | Number of blank nodes check for WarSampo took 17.98565912246704s
Security | Check HTTPS for WarSampo took 0.3902719020843506s
Interpretability | RDF structures check for WarSampo took 0.1943986415863037s
Versatility | Serialization formats check for WarSampo took 0.19203734397888184s
Availability | RDF dump link check for WarSampo took 1.3118858337402344s
License | MR license check for WarSampo took 0.18639206886291504s
License | HR license check for WarSampo took 41.799052238464355s
Amount of data | Number of property check for WarSampo took 0.19811391830444336s
Understandability | Number of label check for WarSampo took 9.069108963012695s
Understandability | URI regex check for WarSampo took 0.3826277256011963s
Understandability | Vocabs check for WarSampo took 0.16309404373168945s
Verifiability | Authors check for WarSampo took 0.19903874397277832s
Verifiability | Publishers check for WarSampo took 0.20555615425109863s
Performance | Throughput check for WarSampo took 11.53515887260437s
Amount of data | Check the number of entities for WarSampo took 17.28584933280945s
Verifiability | Contribs. check for WarSampo took 0.20425009727478027s
Interlinking | sameAs chians check for WarSampo took 0.2306218147277832s
Interlinking | skos check for WarSampo took 0.20836472511291504s
Interlinking | skos check for WarSampo took 0.16350698471069336s
Timeliness | dataset update frequency check for WarSampo took 0.16399407386779785s
Currency | Creation date check for WarSampo took 0.3777806758880615s
Currency | Modification date check for WarSampo took 0.38223862648010254s
Rep.Conc. | URIs length for WarSampo took 49.0429801940918s
Interoperability | New vocabularies check for WarSampo took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.1983654499053955s
Accuracy | Check Functional Property for WarSampo took 0.2030782699584961s
Accuracy | Check Inverse Functional Property for WarSampo took 0.17695927619934082s
Accuracy | Check Empty annotation labels for WarSampo took 11.565743923187256s
Accuracy | Check White space in annotation for WarSampo took 2.2641468048095703s
Accuracy | Check Datatype consistency for WarSampo took 5.513979434967041s
Consistency | Disjoint class check for WarSampo took 0.19368648529052734s
Consistency | Check Misplaced properties for WarSampo took 20.58522605895996s
Consistency | Check Ontology hijacking for WarSampo took 20.679781198501587s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.514432430267334s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.743654727935791s
Conciseness | Check Extensional conciseness for WarSampo took 2.8664886951446533s
Conciseness | Check Intensional conciseness for WarSampo took 0.28246617317199707s
Security | Sign check for WarSampo took 0.1641535758972168s
Availability | Check URIs Dereferenciability for WarSampo took 2.570824384689331s
Completeness | Calculation of interlinking completeness for WarSampo took 0.4170830249786377s
Reputation | Calculation of the PageRank for WarSampo took 0.02159714698791504s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0008270740509033203s
Interlinking | Calculation of Clustering coefficient for WarSampo took 0.00010156631469726562s
Interoperability | Check the re-using of existing vocabs for WarSampo took 1.9073486328125e-06s
Believability | Calculation of trust value for WarSampo took 1.3589859008789062e-05s
INFO | --- Analysis for warsampo took 984.1437921524048s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.343499183654785s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.2943611145019531s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.022481441497802734s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0008134841918945312s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 9.465217590332031e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 1.2636184692382812e-05s
INFO | --- Analysis for wasabi took 55.56944394111633s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 0.580784797668457s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.000568389892578125s
Extra | Recovery of all triples for FAO water areas classification as linked data @PSNC took 120.62243914604187s
Performance | Total latancy measurement for FAO water areas classification as linked data @PSNC took 0.9398036003112793s
Amount of data | Number of triples check for FAO water areas classification as linked data @PSNC took 9.429185152053833s
Interoperability | New terms check for FAO water areas classification as linked data @PSNC took 14.18213677406311s
Versatility | Languages check for FAO water areas classification as linked data @PSNC took 300.2408621311188s
Interpretability | Number of blank nodes check for FAO water areas classification as linked data @PSNC took 2.1227951049804688s
Interpretability | RDF structures check for FAO water areas classification as linked data @PSNC took 0.33918094635009766s
Versatility | Serialization formats check for FAO water areas classification as linked data @PSNC took 9.551083087921143s
Availability | RDF dump link check for FAO water areas classification as linked data @PSNC took 0.36406445503234863s
License | MR license check for FAO water areas classification as linked data @PSNC took 0.8337798118591309s
License | HR license check for FAO water areas classification as linked data @PSNC took 300.2352840900421s
Amount of data | Number of property check for FAO water areas classification as linked data @PSNC took 0.213670015335083s
Understandability | Number of label check for FAO water areas classification as linked data @PSNC took 3.075120687484741s
Understandability | URI regex check for FAO water areas classification as linked data @PSNC took 1.2816612720489502s
Understandability | Vocabs check for FAO water areas classification as linked data @PSNC took 0.6277458667755127s
Verifiability | Authors check for FAO water areas classification as linked data @PSNC took 0.22687768936157227s
Verifiability | Publishers check for FAO water areas classification as linked data @PSNC took 0.25235748291015625s
Performance | Throughput check for FAO water areas classification as linked data @PSNC took 11.208379030227661s
Amount of data | Check the number of entities for FAO water areas classification as linked data @PSNC took 8.416175842285156e-05s
Verifiability | Contribs. check for FAO water areas classification as linked data @PSNC took 0.202256441116333s
Interlinking | sameAs chians check for FAO water areas classification as linked data @PSNC took 0.19312143325805664s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.49858832359313965s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.4206697940826416s
Timeliness | dataset update frequency check for FAO water areas classification as linked data @PSNC took 4.5226054191589355s
Currency | Creation date check for FAO water areas classification as linked data @PSNC took 0.4750821590423584s
Currency | Modification date check for FAO water areas classification as linked data @PSNC took 0.23778533935546875s
Rep.Conc. | URIs length for FAO water areas classification as linked data @PSNC took 155.07445621490479s
Interoperability | New vocabularies check for FAO water areas classification as linked data @PSNC took 1.239776611328125e-05s
Consistency | Deprecated classes/propertiers check for FAO water areas classification as linked data @PSNC took 0.18764948844909668s
Accuracy | Check Functional Property for FAO water areas classification as linked data @PSNC took 0.49640750885009766s
Accuracy | Check Inverse Functional Property for FAO water areas classification as linked data @PSNC took 0.47078371047973633s
Accuracy | Check Empty annotation labels for FAO water areas classification as linked data @PSNC took 46.83005928993225s
Accuracy | Check White space in annotation for FAO water areas classification as linked data @PSNC took 2.7080512046813965s
Accuracy | Check Datatype consistency for FAO water areas classification as linked data @PSNC took 2.717743158340454s
Consistency | Disjoint class check for FAO water areas classification as linked data @PSNC took 0.19898676872253418s
Consistency | Check Misplaced properties for FAO water areas classification as linked data @PSNC took 86.26530528068542s
Consistency | Misplaced classes for FAO water areas classification as linked data @PSNC took 8.49788761138916s
Consistency | Check Ontology hijacking for FAO water areas classification as linked data @PSNC took 40.93864107131958s
Consistency | Check Invalid usage of undefined classes for FAO water areas classification as linked data @PSNC took 1.513657808303833s
Consistency | Check Invalid usage of undefined properties for FAO water areas classification as linked data @PSNC took 87.72365403175354s
Conciseness | Check Extensional conciseness for FAO water areas classification as linked data @PSNC took 2.7866296768188477s
Conciseness | Check Intensional conciseness for FAO water areas classification as linked data @PSNC took 0.6752541065216064s
Security | Sign check for FAO water areas classification as linked data @PSNC took 1.407451868057251s
Availability | Check URIs Dereferenciability for FAO water areas classification as linked data @PSNC took 10.15865182876587s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.3747849464416504s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.02152848243713379s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 4.363059997558594e-05s
Interoperability | Check the re-using of existing vocabs for FAO water areas classification as linked data @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for Water_Areas_Classification took 2360.5490243434906s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 0.19095969200134277s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.0005779266357421875s
Extra | Recovery of all triples for Water buffer dataset from Czech Republic @PSNC took 118.59077143669128s
Performance | Total latancy measurement for Water buffer dataset from Czech Republic @PSNC took 0.9772775173187256s
Amount of data | Number of triples check for Water buffer dataset from Czech Republic @PSNC took 9.00992488861084s
Interoperability | New terms check for Water buffer dataset from Czech Republic @PSNC took 14.289746046066284s
Versatility | Languages check for Water buffer dataset from Czech Republic @PSNC took 300.2145788669586s
Interpretability | Number of blank nodes check for Water buffer dataset from Czech Republic @PSNC took 1.9970510005950928s
Interpretability | RDF structures check for Water buffer dataset from Czech Republic @PSNC took 0.39057445526123047s
Versatility | Serialization formats check for Water buffer dataset from Czech Republic @PSNC took 9.40020203590393s
Availability | RDF dump link check for Water buffer dataset from Czech Republic @PSNC took 0.4591522216796875s
License | MR license check for Water buffer dataset from Czech Republic @PSNC took 0.19488906860351562s
License | HR license check for Water buffer dataset from Czech Republic @PSNC took 300.2596592903137s
Amount of data | Number of property check for Water buffer dataset from Czech Republic @PSNC took 0.24895977973937988s
Understandability | Number of label check for Water buffer dataset from Czech Republic @PSNC took 1.315098524093628s
Understandability | URI regex check for Water buffer dataset from Czech Republic @PSNC took 1.029261589050293s
Understandability | Vocabs check for Water buffer dataset from Czech Republic @PSNC took 0.450359582901001s
Verifiability | Authors check for Water buffer dataset from Czech Republic @PSNC took 0.22558116912841797s
Verifiability | Publishers check for Water buffer dataset from Czech Republic @PSNC took 0.2691621780395508s
Performance | Throughput check for Water buffer dataset from Czech Republic @PSNC took 11.044661045074463s
Amount of data | Check the number of entities for Water buffer dataset from Czech Republic @PSNC took 0.00013256072998046875s
Verifiability | Contribs. check for Water buffer dataset from Czech Republic @PSNC took 0.23803925514221191s
Interlinking | sameAs chians check for Water buffer dataset from Czech Republic @PSNC took 0.20256447792053223s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.4237067699432373s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.4427144527435303s
Timeliness | dataset update frequency check for Water buffer dataset from Czech Republic @PSNC took 8.987411499023438s
Currency | Creation date check for Water buffer dataset from Czech Republic @PSNC took 0.4881727695465088s
Currency | Modification date check for Water buffer dataset from Czech Republic @PSNC took 0.2467191219329834s
Rep.Conc. | URIs length for Water buffer dataset from Czech Republic @PSNC took 193.97896885871887s
Interoperability | New vocabularies check for Water buffer dataset from Czech Republic @PSNC took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for Water buffer dataset from Czech Republic @PSNC took 0.23715472221374512s
Accuracy | Check Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.2559785842895508s
Accuracy | Check Inverse Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.26758718490600586s
Accuracy | Check Empty annotation labels for Water buffer dataset from Czech Republic @PSNC took 60.382383823394775s
Accuracy | Check White space in annotation for Water buffer dataset from Czech Republic @PSNC took 2.715742349624634s
Accuracy | Check Datatype consistency for Water buffer dataset from Czech Republic @PSNC took 2.849940061569214s
Consistency | Disjoint class check for Water buffer dataset from Czech Republic @PSNC took 0.21222209930419922s
Consistency | Check Misplaced properties for Water buffer dataset from Czech Republic @PSNC took 86.66957926750183s
Consistency | Misplaced classes for Water buffer dataset from Czech Republic @PSNC took 8.67588186264038s
Consistency | Check Ontology hijacking for Water buffer dataset from Czech Republic @PSNC took 39.994765281677246s
Consistency | Check Invalid usage of undefined classes for Water buffer dataset from Czech Republic @PSNC took 1.5157217979431152s
Consistency | Check Invalid usage of undefined properties for Water buffer dataset from Czech Republic @PSNC took 87.28806495666504s
Conciseness | Check Extensional conciseness for Water buffer dataset from Czech Republic @PSNC took 2.822831630706787s
Conciseness | Check Intensional conciseness for Water buffer dataset from Czech Republic @PSNC took 0.5543169975280762s
Security | Sign check for Water buffer dataset from Czech Republic @PSNC took 0.9003207683563232s
Availability | Check URIs Dereferenciability for Water buffer dataset from Czech Republic @PSNC took 9.136124849319458s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.3507857322692871s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.022307872772216797s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 0.00011038780212402344s
Interoperability | Check the re-using of existing vocabs for Water buffer dataset from Czech Republic @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 1.4066696166992188e-05s
INFO | --- Analysis for Water_Buffer took 2351.012869119644s
Availability | SPARQL endpoint availability check for WebIsALOD took 0.2195601463317871s
Availability | VoID file availability check for WebIsALOD took 0.0007569789886474609s
Extra | Recovery of all triples for WebIsALOD took 1.3764240741729736s
Performance | Total latancy measurement for WebIsALOD took 0.48485851287841797s
Amount of data | Number of triples check for WebIsALOD took 26.93649387359619s
Interoperability | New terms check for WebIsALOD took 20.76232624053955s
Versatility | Languages check for WebIsALOD took 60.64804172515869s
Interpretability | Number of blank nodes check for WebIsALOD took 0.1257028579711914s
Interpretability | RDF structures check for WebIsALOD took 0.19605135917663574s
Versatility | Serialization formats check for WebIsALOD took 0.135908842086792s
Availability | RDF dump link check for WebIsALOD took 1.4415571689605713s
License | MR license check for WebIsALOD took 0.1305692195892334s
License | HR license check for WebIsALOD took 34.38322448730469s
Amount of data | Number of property check for WebIsALOD took 0.1280214786529541s
Understandability | Number of label check for WebIsALOD took 0.2898869514465332s
Understandability | URI regex check for WebIsALOD took 0.19278907775878906s
Understandability | Vocabs check for WebIsALOD took 0.141798734664917s
Verifiability | Authors check for WebIsALOD took 0.14291763305664062s
Verifiability | Publishers check for WebIsALOD took 0.12726998329162598s
Performance | Throughput check for WebIsALOD took 10.328227758407593s
Amount of data | Check the number of entities for WebIsALOD took 0.00012350082397460938s
Verifiability | Contribs. check for WebIsALOD took 0.1282048225402832s
Interlinking | sameAs chians check for WebIsALOD took 0.1691892147064209s
Interlinking | skos check for WebIsALOD took 0.15201878547668457s
Interlinking | skos check for WebIsALOD took 0.09963321685791016s
Timeliness | dataset update frequency check for WebIsALOD took 0.10838842391967773s
Currency | Creation date check for WebIsALOD took 0.2715458869934082s
Currency | Modification date check for WebIsALOD took 0.23105740547180176s
Rep.Conc. | URIs length for WebIsALOD took 80.1284589767456s
Interoperability | New vocabularies check for WebIsALOD took 4.715120792388916s
Consistency | Deprecated classes/propertiers check for WebIsALOD took 65.46694612503052s
Accuracy | Check Functional Property for WebIsALOD took 1.3867201805114746s
Accuracy | Check Inverse Functional Property for WebIsALOD took 0.15440750122070312s
Accuracy | Check Empty annotation labels for WebIsALOD took 0.6753506660461426s
Accuracy | Check White space in annotation for WebIsALOD took 0.030425548553466797s
Accuracy | Check Datatype consistency for WebIsALOD took 0.03163599967956543s
Consistency | Disjoint class check for WebIsALOD took 2.435702323913574s
Consistency | Check Misplaced properties for WebIsALOD took 62.46570897102356s
Consistency | Misplaced classes for WebIsALOD took 0.28450512886047363s
Consistency | Check Ontology hijacking for WebIsALOD took 2.2993013858795166s
Consistency | Check Invalid usage of undefined classes for WebIsALOD took 1.672804594039917s
Consistency | Check Invalid usage of undefined properties for WebIsALOD took 63.6146981716156s
Conciseness | Check Extensional conciseness for WebIsALOD took 0.034058570861816406s
Conciseness | Check Intensional conciseness for WebIsALOD took 9.777708292007446s
Security | Sign check for WebIsALOD took 0.4236781597137451s
Availability | Check URIs Dereferenciability for WebIsALOD took 10.71262240409851s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.37308454513549805s
Reputation | Calculation of the PageRank for WebIsALOD took 0.023403406143188477s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 0.00014591217041015625s
Interoperability | Check the re-using of existing vocabs for WebIsALOD took 3.7146382331848145s
Believability | Calculation of trust value for WebIsALOD took 1.3589859008789062e-05s
INFO | --- Analysis for webisalod took 720.1307239532471s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 0.00016045570373535156s
Availability | VoID file availability check for webnmasunotraveler took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.30861759185791016s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.021436214447021484s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 4.744529724121094e-05s
Believability | Calculation of trust value for webnmasunotraveler took 6.127357482910156e-05s
INFO | --- Analysis for webnmasunotraveler took 9.64291262626648s
Availability | SPARQL endpoint availability check for Whisky Circle took 0.00010085105895996094s
Availability | VoID file availability check for Whisky Circle took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.3173403739929199s
Reputation | Calculation of the PageRank for Whisky Circle took 0.020931720733642578s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00010776519775390625s
Believability | Calculation of trust value for Whisky Circle took 1.6927719116210938e-05s
INFO | --- Analysis for whisky-circle-info took 3.5842013359069824s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 12.182359218597412s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.0008392333984375s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.334301233291626s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.032796382904052734s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0011930465698242188s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 4.7206878662109375e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for WHOnto took 29.68342423439026s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 9.298324584960938e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0007779598236083984s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.3318769931793213s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.022591352462768555s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.001168966293334961s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 4.315376281738281e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for whonto took 9.62887167930603s
Availability | SPARQL endpoint availability check for Wikidata took 0.47968602180480957s
Availability | VoID file availability check for Wikidata took 0.0006883144378662109s
Extra | Recovery of all triples for Wikidata took 67.87147951126099s
Performance | Total latancy measurement for Wikidata took 1.155980110168457s
Amount of data | Number of triples check for Wikidata took 65.17737340927124s
Interoperability | New terms check for Wikidata took 1.9340858459472656s
Versatility | Languages check for Wikidata took 65.17014837265015s
Interpretability | Number of blank nodes check for Wikidata took 65.16521310806274s
Interpretability | RDF structures check for Wikidata took 0.22916674613952637s
Versatility | Serialization formats check for Wikidata took 0.3278822898864746s
Availability | RDF dump link check for Wikidata took 0.16890501976013184s
License | MR license check for Wikidata took 0.18023180961608887s
License | HR license check for Wikidata took 65.17103624343872s
Amount of data | Number of property check for Wikidata took 0.2814176082611084s
Understandability | Number of label check for Wikidata took 60.18088960647583s
Understandability | URI regex check for Wikidata took 0.496837854385376s
Understandability | Vocabs check for Wikidata took 0.1683962345123291s
Verifiability | Authors check for Wikidata took 0.3529067039489746s
Verifiability | Publishers check for Wikidata took 0.3474092483520508s
Amount of data | Check the number of entities for Wikidata took 3.337860107421875e-05s
Verifiability | Contribs. check for Wikidata took 0.1722733974456787s
Interlinking | sameAs chians check for Wikidata took 14.467413425445557s
Interlinking | skos check for Wikidata took 0.24686789512634277s
Interlinking | skos check for Wikidata took 0.2643578052520752s
Timeliness | dataset update frequency check for Wikidata took 0.19571661949157715s
Currency | Creation date check for Wikidata took 0.41847729682922363s
Currency | Modification date check for Wikidata took 0.4762754440307617s
Rep.Conc. | URIs length for Wikidata took 27.585747003555298s
Interoperability | New vocabularies check for Wikidata took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for Wikidata took 0.18882226943969727s
Accuracy | Check Empty annotation labels for Wikidata took 15.62471866607666s
Accuracy | Check White space in annotation for Wikidata took 2.6800360679626465s
Consistency | Disjoint class check for Wikidata took 0.1863851547241211s
Consistency | Check Misplaced properties for Wikidata took 15.588329076766968s
Consistency | Misplaced classes for Wikidata took 1.1482760906219482s
Consistency | Check Ontology hijacking for Wikidata took 25.458547592163086s
Consistency | Check Invalid usage of undefined properties for Wikidata took 9.962885618209839s
Conciseness | Check Extensional conciseness for Wikidata took 0.00018858909606933594s
Conciseness | Check Intensional conciseness for Wikidata took 1.7136497497558594s
Security | Sign check for Wikidata took 0.22499418258666992s
Completeness | Calculation of interlinking completeness for Wikidata took 0.4098083972930908s
Reputation | Calculation of the PageRank for Wikidata took 0.02163839340209961s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.0003159046173095703s
Interoperability | Check the re-using of existing vocabs for Wikidata took 1.430511474609375e-06s
Believability | Calculation of trust value for Wikidata took 5.9604644775390625e-06s
INFO | --- Analysis for wikidata took 804.7401492595673s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 7.033348083496094e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.307509183883667s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.02159595489501953s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 7.295608520507812e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 7.62939453125e-06s
INFO | --- Analysis for wikilinks-rdf-nif took 2.985771656036377s
Availability | SPARQL endpoint availability check for WikiPathways took 7.414817810058594e-05s
Availability | VoID file availability check for WikiPathways took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.34088754653930664s
Reputation | Calculation of the PageRank for WikiPathways took 0.021597862243652344s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 3.4332275390625e-05s
Believability | Calculation of trust value for WikiPathways took 1.5735626220703125e-05s
INFO | --- Analysis for wikipathways took 3.9823505878448486s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.27175188064575195s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.4212677478790283s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.021034955978393555s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 9.512901306152344e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 8.344650268554688e-06s
INFO | --- Analysis for wiktionary-dbpedia-org took 4.779097080230713s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.1940996646881104s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.32534360885620117s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.02226114273071289s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.457069396972656e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 1.2159347534179688e-05s
INFO | --- Analysis for wl-kg took 4.378481149673462s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.00010180473327636719s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007159709930419922s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.3402676582336426s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.02129507064819336s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 7.653236389160156e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 1.239776611328125e-05s
INFO | --- Analysis for wn-wiki-instances took 3.591456413269043s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.12129521369934082s
Availability | VoID file availability check for World Loanword Database took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.30777788162231445s
Reputation | Calculation of the PageRank for World Loanword Database took 0.022974252700805664s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 7.748603820800781e-05s
Believability | Calculation of trust value for World Loanword Database took 1.3113021850585938e-05s
INFO | --- Analysis for wold took 3.205254316329956s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 0.00023889541625976562s
Availability | VoID file availability check for Wood Trick LLC took 0.0006551742553710938s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.347836971282959s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.021184682846069336s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 3.314018249511719e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.239776611328125e-05s
INFO | --- Analysis for woodtrick took 3.616469621658325s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 0.49955224990844727s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.298534631729126s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.021141529083251953s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 4.0531158447265625e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 5.7220458984375e-06s
INFO | --- Analysis for WordFormationLatin took 4.507909536361694s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 0.000110626220703125s
Availability | VoID file availability check for WordLift Blog EN took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.3379645347595215s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.0001049041748046875s
Believability | Calculation of trust value for WordLift Blog EN took 1.1444091796875e-05s
INFO | --- Analysis for wordlift-io-blog-en took 3.827063798904419s
Availability | SPARQL endpoint availability check for WordLift IT took 9.632110595703125e-05s
Availability | VoID file availability check for WordLift IT took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.7167255878448486s
Reputation | Calculation of the PageRank for WordLift IT took 0.021439313888549805s
Interlinking | Calculation of Degree of Connection for WordLift IT took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for WordLift IT took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00012087821960449219s
Believability | Calculation of trust value for WordLift IT took 1.3113021850585938e-05s
INFO | --- Analysis for wordlift-io-blog-it took 6.052174806594849s
Availability | SPARQL endpoint availability check for WordNet-RDF took 0.000148773193359375s
Availability | VoID file availability check for WordNet-RDF took 0.0007920265197753906s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.31621551513671875s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.021456241607666016s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.870529174804688e-05s
Believability | Calculation of trust value for WordNet-RDF took 1.4781951904296875e-05s
INFO | --- Analysis for wordnet-rdf took 3.043002128601074s
Availability | SPARQL endpoint availability check for wordpress took 8.96453857421875e-05s
Availability | VoID file availability check for wordpress took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for wordpress took 0.29944396018981934s
Reputation | Calculation of the PageRank for wordpress took 0.020999431610107422s
Interlinking | Calculation of Degree of Connection for wordpress took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for wordpress took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.916854858398438e-05s
Believability | Calculation of trust value for wordpress took 1.0013580322265625e-05s
INFO | --- Analysis for wordpress took 4.371285676956177s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 0.24751496315002441s
Availability | VoID file availability check for World Bank Linked Data took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.5808060169219971s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.020824193954467773s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.0001266002655029297s
Believability | Calculation of trust value for World Bank Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for world-bank-linked-data took 5.884023666381836s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 1.0119879245758057s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.669182300567627s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.02396106719970703s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 9.369850158691406e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 1.0728836059570312e-05s
INFO | --- Analysis for world-factbook-fu-berlin took 11.307313919067383s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 4.482269287109375e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0007472038269042969s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.30663323402404785s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.021556615829467773s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 9.799003601074219e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 9.059906005859375e-06s
INFO | --- Analysis for world-wide-web-foundation took 6.278249740600586s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.3538541793823242s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0005197525024414062s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 2.5324652194976807s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.8371274471282959s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.23870563507080078s
Interoperability | New terms check for World War 1 as Linked Open Data took 1.6869730949401855s
Versatility | Languages check for World War 1 as Linked Open Data took 0.35282373428344727s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.23646330833435059s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.40233850479125977s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.3083209991455078s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.2690436840057373s
Availability | RDF dump link check for World War 1 as Linked Open Data took 6.68496036529541s
License | MR license check for World War 1 as Linked Open Data took 0.19971275329589844s
License | HR license check for World War 1 as Linked Open Data took 1.5963871479034424s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.19005846977233887s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.4291980266571045s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.5024464130401611s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.24674415588378906s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.1920609474182129s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.19217276573181152s
Performance | Throughput check for World War 1 as Linked Open Data took 11.208563804626465s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.07944846153259277s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.19188642501831055s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.2356586456298828s
Interlinking | skos check for World War 1 as Linked Open Data took 0.1927933692932129s
Interlinking | skos check for World War 1 as Linked Open Data took 0.14902377128601074s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.18732929229736328s
Currency | Creation date check for World War 1 as Linked Open Data took 0.3757047653198242s
Currency | Modification date check for World War 1 as Linked Open Data took 0.19359135627746582s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 2.024259328842163s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 7.691303730010986s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.21556329727172852s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.18761491775512695s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.16525912284851074s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.307908535003662s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.050684213638305664s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.325685977935791s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.1846163272857666s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.6026606559753418s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.1202361583709717s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.3623459339141846s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.5872926712036133s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.19390392303466797s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.6644551753997803s
Security | Sign check for World War 1 as Linked Open Data took 0.1904127597808838s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 4.918229103088379s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.4385097026824951s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.020917177200317383s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 9.083747863769531e-05s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 10.02408480644226s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 1.3113021850585938e-05s
INFO | --- Analysis for ww1lod took 93.42843914031982s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.36371541023254395s
Availability | VoID file availability check for xLiD-Lexica took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.385451078414917s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.021291732788085938s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 7.176399230957031e-05s
Believability | Calculation of trust value for xLiD-Lexica took 8.106231689453125e-06s
INFO | --- Analysis for xlid-lexica took 4.8376665115356445s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 4.458427429199219e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.30631089210510254s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.021131515502929688s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0008232593536376953s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 4.5299530029296875e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 7.867813110351562e-06s
INFO | --- Analysis for xwn took 3.6411190032958984s
Availability | SPARQL endpoint availability check for xxx took 4.38690185546875e-05s
Availability | VoID file availability check for xxx took 0.0002987384796142578s
Completeness | Calculation of interlinking completeness for xxx took 0.3504056930541992s
Reputation | Calculation of the PageRank for xxx took 0.02127385139465332s
Interlinking | Calculation of Degree of Connection for xxx took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for xxx took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for xxx took 3.6716461181640625e-05s
Believability | Calculation of trust value for xxx took 8.344650268554688e-06s
INFO | --- Analysis for xx took 2.9445226192474365s
Availability | SPARQL endpoint availability check for YAGO took 8.988380432128906e-05s
Availability | VoID file availability check for YAGO took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for YAGO took 0.3160994052886963s
Reputation | Calculation of the PageRank for YAGO took 0.02148294448852539s
Interlinking | Calculation of Degree of Connection for YAGO took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.0001366138458251953s
Believability | Calculation of trust value for YAGO took 1.2159347534179688e-05s
INFO | --- Analysis for yago took 4.86951756477356s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 1.5858204364776611s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.33956027030944824s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.021010160446166992s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 8.058547973632812e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 1.1920928955078125e-05s
INFO | --- Analysis for yahoo_geoplanet took 11.085070371627808s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.16797780990600586s
Availability | VoID file availability check for Yale Senselab took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.32907605171203613s
Reputation | Calculation of the PageRank for Yale Senselab took 0.0209653377532959s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 3.24249267578125e-05s
Believability | Calculation of trust value for Yale Senselab took 1.0251998901367188e-05s
INFO | --- Analysis for yale_senselab took 12.395241260528564s
Availability | SPARQL endpoint availability check for test-dapp-2 took 9.131431579589844e-05s
Availability | VoID file availability check for test-dapp-2 took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.31955528259277344s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.020849227905273438s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 3.147125244140625e-05s
Believability | Calculation of trust value for test-dapp-2 took 1.0967254638671875e-05s
INFO | --- Analysis for yordhis took 2.9376461505889893s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 0.8136379718780518s
Availability | VoID file availability check for Yovisto - academic video search took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.4572434425354004s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.02082037925720215s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.985664367675781e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 9.298324584960938e-06s
INFO | --- Analysis for yovisto took 24.178784608840942s
Availability | SPARQL endpoint availability check for Yleinen suomalainen asiasanasto - YSA took 8.988380432128906e-05s
Availability | VoID file availability check for Yleinen suomalainen asiasanasto - YSA took 0.0007712841033935547s
Completeness | Calculation of interlinking completeness for Yleinen suomalainen asiasanasto - YSA took 0.31667447090148926s
Reputation | Calculation of the PageRank for Yleinen suomalainen asiasanasto - YSA took 0.022971391677856445s
Interlinking | Calculation of Degree of Connection for Yleinen suomalainen asiasanasto - YSA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Yleinen suomalainen asiasanasto - YSA took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Yleinen suomalainen asiasanasto - YSA took 3.552436828613281e-05s
Believability | Calculation of trust value for Yleinen suomalainen asiasanasto - YSA took 1.1682510375976562e-05s
INFO | --- Analysis for ysa took 4.41620397567749s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 9.107589721679688e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.4058115482330322s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.02088451385498047s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.435943603515625e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for yso took 5.048931121826172s
Availability | SPARQL endpoint availability check for yso-fi-allars took 9.083747863769531e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.4409370422363281s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.022481203079223633s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.600120544433594e-05s
Believability | Calculation of trust value for yso-fi-allars took 1.0967254638671875e-05s
INFO | --- Analysis for yso-fi-allars took 3.774169445037842s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 9.059906005859375e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0008025169372558594s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.3131866455078125s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.02245473861694336s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 4.029273986816406e-05s
Believability | Calculation of trust value for yso-fi-ysa took 1.1444091796875e-05s
INFO | --- Analysis for yso-fi-ysa took 3.548064708709717s
Availability | SPARQL endpoint availability check for YSO places took 0.672450065612793s
Availability | VoID file availability check for YSO places took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for YSO places took 0.3359236717224121s
Reputation | Calculation of the PageRank for YSO places took 0.020844221115112305s
Interlinking | Calculation of Degree of Connection for YSO places took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for YSO places took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for YSO places took 3.24249267578125e-05s
Believability | Calculation of trust value for YSO places took 1.0728836059570312e-05s
INFO | --- Analysis for yso-paikat took 4.882404565811157s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 5.555152893066406e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.3441128730773926s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.02220463752746582s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.5762786865234375e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 9.775161743164062e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 7.111400842666626s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 9.131431579589844e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.32801222801208496s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.02099299430847168s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.4332275390625e-05s
Believability | Calculation of trust value for zaragoza_turruta took 1.0728836059570312e-05s
INFO | --- Analysis for zaragoza_turruta took 3.6051883697509766s
Availability | SPARQL endpoint availability check for ZBW Labs took 0.00013327598571777344s
Availability | VoID file availability check for ZBW Labs took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.32711076736450195s
Reputation | Calculation of the PageRank for ZBW Labs took 0.02090144157409668s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 6.794929504394531e-05s
Believability | Calculation of trust value for ZBW Labs took 1.0967254638671875e-05s
INFO | --- Analysis for zbw-labs took 4.366067886352539s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.20297980308532715s
Availability | VoID file availability check for 20th Century Press Archives took 0.0005807876586914062s
Extra | Recovery of all triples for 20th Century Press Archives took 35.90753126144409s
Performance | Total latancy measurement for 20th Century Press Archives took 0.9276626110076904s
Amount of data | Number of triples check for 20th Century Press Archives took 3.840531587600708s
Interoperability | New terms check for 20th Century Press Archives took 2.0123941898345947s
Versatility | Languages check for 20th Century Press Archives took 10.622230768203735s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 1.7281901836395264s
Interpretability | RDF structures check for 20th Century Press Archives took 0.17190980911254883s
Versatility | Serialization formats check for 20th Century Press Archives took 0.23839235305786133s
Availability | RDF dump link check for 20th Century Press Archives took 0.13028526306152344s
License | MR license check for 20th Century Press Archives took 0.12789297103881836s
License | HR license check for 20th Century Press Archives took 8.974122285842896s
Amount of data | Number of property check for 20th Century Press Archives took 0.1614551544189453s
Understandability | Number of label check for 20th Century Press Archives took 0.9233484268188477s
Understandability | URI regex check for 20th Century Press Archives took 0.3238503932952881s
Understandability | Vocabs check for 20th Century Press Archives took 0.14747071266174316s
Verifiability | Authors check for 20th Century Press Archives took 0.15514731407165527s
Verifiability | Publishers check for 20th Century Press Archives took 0.1297008991241455s
Performance | Throughput check for 20th Century Press Archives took 10.59841513633728s
Amount of data | Check the number of entities for 20th Century Press Archives took 8.821487426757812e-05s
Verifiability | Contribs. check for 20th Century Press Archives took 0.1378941535949707s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.16161513328552246s
Interlinking | skos check for 20th Century Press Archives took 0.21946120262145996s
Interlinking | skos check for 20th Century Press Archives took 0.22403907775878906s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.2817113399505615s
Currency | Creation date check for 20th Century Press Archives took 0.276996374130249s
Currency | Modification date check for 20th Century Press Archives took 0.2705094814300537s
Rep.Conc. | URIs length for 20th Century Press Archives took 18.47893261909485s
Interoperability | New vocabularies check for 20th Century Press Archives took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.18700742721557617s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.15958476066589355s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.16380095481872559s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 5.62518310546875s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8994503021240234s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.261721611022949s
Consistency | Disjoint class check for 20th Century Press Archives took 0.15471506118774414s
Consistency | Check Misplaced properties for 20th Century Press Archives took 3.316999673843384s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.9863874912261963s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 7.178250789642334s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 4.981812238693237s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.8476555347442627s
Security | Sign check for 20th Century Press Archives took 0.13623976707458496s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 985.8323709964752s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 1.1387429237365723s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.021483898162841797s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00012111663818359375s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 1.6689300537109375e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 1.2159347534179688e-05s
INFO | --- Analysis for zbw-pressemappe20 took 1140.520797252655s
Availability | SPARQL endpoint availability check for zhishi.lemon took 0.00010848045349121094s
Availability | VoID file availability check for zhishi.lemon took 0.0007622241973876953s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.35721850395202637s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.021260738372802734s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 5.030632019042969e-05s
Believability | Calculation of trust value for zhishi.lemon took 9.059906005859375e-06s
INFO | --- Analysis for zhishi-lemon took 25.50774312019348s
Availability | SPARQL endpoint availability check for Zhishi.me took 3.503225088119507s
Availability | VoID file availability check for Zhishi.me took 0.0012631416320800781s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.343472957611084s
Reputation | Calculation of the PageRank for Zhishi.me took 0.02098822593688965s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 8.0108642578125e-05s
Believability | Calculation of trust value for Zhishi.me took 1.239776611328125e-05s
INFO | --- Analysis for zhishi-me took 9.123557090759277s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 0.00012063980102539062s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.30066800117492676s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.021646738052368164s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 7.2479248046875e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 1.3589859008789062e-05s
INFO | --- Analysis for zitgist-musicbrainz took 3.5607094764709473s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 0.00012612342834472656s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.33115601539611816s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.02086472511291504s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 3.3855438232421875e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 1.1205673217773438e-05s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 3.225252389907837s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.3190009593963623s
Availability | VoID file availability check for performing-arts.ch took 0.0005183219909667969s
Extra | Recovery of all triples for performing-arts.ch took 15.882109642028809s
Performance | Total latancy measurement for performing-arts.ch took 0.7538821697235107s
Amount of data | Number of triples check for performing-arts.ch took 40.669299364089966s
Interoperability | New terms check for performing-arts.ch took 1.5675749778747559s
Versatility | Languages check for performing-arts.ch took 60.147311210632324s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.14235019683838s
Interpretability | RDF structures check for performing-arts.ch took 0.14572453498840332s
Versatility | Serialization formats check for performing-arts.ch took 0.17038631439208984s
Availability | RDF dump link check for performing-arts.ch took 0.15557336807250977s
License | MR license check for performing-arts.ch took 0.17431306838989258s
License | HR license check for performing-arts.ch took 60.136061668395996s
Amount of data | Number of property check for performing-arts.ch took 0.2252342700958252s
Understandability | Number of label check for performing-arts.ch took 27.728282928466797s
Understandability | URI regex check for performing-arts.ch took 0.29302048683166504s
Understandability | Vocabs check for performing-arts.ch took 0.1491692066192627s
Verifiability | Authors check for performing-arts.ch took 0.18898940086364746s
Verifiability | Publishers check for performing-arts.ch took 0.15964508056640625s
Performance | Throughput check for performing-arts.ch took 10.753172874450684s
Amount of data | Check the number of entities for performing-arts.ch took 7.152557373046875e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.16280341148376465s
Interlinking | sameAs chians check for performing-arts.ch took 0.656721830368042s
Interlinking | skos check for performing-arts.ch took 0.17796611785888672s
Interlinking | skos check for performing-arts.ch took 0.18634867668151855s
Timeliness | dataset update frequency check for performing-arts.ch took 0.178816556930542s
Currency | Creation date check for performing-arts.ch took 0.33060145378112793s
Currency | Modification date check for performing-arts.ch took 0.3554399013519287s
Rep.Conc. | URIs length for performing-arts.ch took 25.90533185005188s
Interoperability | New vocabularies check for performing-arts.ch took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.14756512641906738s
Accuracy | Check Functional Property for performing-arts.ch took 0.19368791580200195s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.18744802474975586s
Accuracy | Check Empty annotation labels for performing-arts.ch took 35.79839253425598s
Accuracy | Check White space in annotation for performing-arts.ch took 2.553234100341797s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.925936937332153s
Consistency | Disjoint class check for performing-arts.ch took 0.16752195358276367s
Consistency | Check Misplaced properties for performing-arts.ch took 0.40639829635620117s
Consistency | Misplaced classes for performing-arts.ch took 8.663482666015625s
Consistency | Check Ontology hijacking for performing-arts.ch took 47.044310331344604s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 19757.780412197113s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 8.247820615768433s
Conciseness | Check Extensional conciseness for performing-arts.ch took 35.499287366867065s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.5614070892333984s
Security | Sign check for performing-arts.ch took 0.22627830505371094s
Availability | Check URIs Dereferenciability for performing-arts.ch took 4.201969623565674s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 1.1858527660369873s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.6565036773681641s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 0.0011322498321533203s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.001867532730102539s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 0.021689414978027344s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 3.5762786865234375e-06s
Believability | Calculation of trust value for performing-arts.ch took 1.0728836059570312e-05s
INFO | --- Analysis for performing-arts.ch took 20774.64008808136s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.433321237564087s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.3224952220916748s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.048609256744384766s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.621246337890625e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 1.4781951904296875e-05s
INFO | --- Analysis for The-AA-Thesaurus took 9.55731749534607s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.7841041088104248s
Availability | VoID file availability check for MiMoTextBase took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.32997632026672363s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.10699892044067383s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.52587890625e-05s
Believability | Calculation of trust value for MiMoTextBase took 1.3589859008789062e-05s
INFO | --- Analysis for MiMoTextBase took 7.038764238357544s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.5182292461395264s
Availability | VoID file availability check for National Library of Sweden took 0.0006492137908935547s
Extra | Recovery of all triples for National Library of Sweden took 6.4110047817230225s
Performance | Total latancy measurement for National Library of Sweden took 1.088531732559204s
Amount of data | Number of triples check for National Library of Sweden took 22.150949478149414s
Interoperability | New terms check for National Library of Sweden took 18.140989303588867s
Versatility | Languages check for National Library of Sweden took 0.2049710750579834s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.24525594711304s
Interpretability | RDF structures check for National Library of Sweden took 0.2792849540710449s
Versatility | Serialization formats check for National Library of Sweden took 0.22467970848083496s
Availability | RDF dump link check for National Library of Sweden took 0.20132684707641602s
License | MR license check for National Library of Sweden took 0.2526412010192871s
License | HR license check for National Library of Sweden took 0.2743568420410156s
Amount of data | Number of property check for National Library of Sweden took 0.2287447452545166s
Understandability | Number of label check for National Library of Sweden took 0.31064844131469727s
Understandability | URI regex check for National Library of Sweden took 0.44458651542663574s
Understandability | Vocabs check for National Library of Sweden took 0.20966506004333496s
Verifiability | Authors check for National Library of Sweden took 0.22971320152282715s
Verifiability | Publishers check for National Library of Sweden took 0.20826458930969238s
Performance | Throughput check for National Library of Sweden took 10.337600469589233s
Amount of data | Check the number of entities for National Library of Sweden took 7.43865966796875e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.2315843105316162s
Interlinking | sameAs chians check for National Library of Sweden took 0.21110749244689941s
Interlinking | skos check for National Library of Sweden took 0.25734400749206543s
Interlinking | skos check for National Library of Sweden took 0.20670723915100098s
Timeliness | dataset update frequency check for National Library of Sweden took 0.2229294776916504s
Currency | Creation date check for National Library of Sweden took 0.4270198345184326s
Currency | Modification date check for National Library of Sweden took 0.464799165725708s
Rep.Conc. | URIs length for National Library of Sweden took 96.39341163635254s
Interoperability | New vocabularies check for National Library of Sweden took 1.1920928955078125e-05s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.20481109619140625s
Accuracy | Check Functional Property for National Library of Sweden took 0.263413667678833s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.2529010772705078s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.2833068370819092s
Consistency | Disjoint class check for National Library of Sweden took 0.22607779502868652s
Consistency | Check Misplaced properties for National Library of Sweden took 70.8326644897461s
Consistency | Misplaced classes for National Library of Sweden took 1.1695916652679443s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.411416530609131s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.341712236404419s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 71.77334237098694s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.29033470153808594s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.349442720413208s
Security | Sign check for National Library of Sweden took 0.26838064193725586s
Availability | Check URIs Dereferenciability for National Library of Sweden took 10.337396144866943s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.6060621738433838s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.05207514762878418s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 2.0742416381835938e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 2.1457672119140625e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.52587890625e-05s
INFO | --- Analysis for NLS took 1413.1933071613312s
Availability | SPARQL endpoint availability check for Japan Search took 1.4195892810821533s
Availability | VoID file availability check for Japan Search took 0.0005249977111816406s
Extra | Recovery of all triples for Japan Search took 4.1138482093811035s
Performance | Total latancy measurement for Japan Search took 2.5211169719696045s
Amount of data | Number of triples check for Japan Search took 9.639198780059814s
Interoperability | New terms check for Japan Search took 4.2286787033081055s
Versatility | Languages check for Japan Search took 0.2844352722167969s
Interpretability | Number of blank nodes check for Japan Search took 13.510029554367065s
Interpretability | RDF structures check for Japan Search took 0.9245140552520752s
Versatility | Serialization formats check for Japan Search took 0.46793389320373535s
Availability | RDF dump link check for Japan Search took 0.3395869731903076s
License | MR license check for Japan Search took 1.0521626472473145s
License | HR license check for Japan Search took 91.56555032730103s
Amount of data | Number of property check for Japan Search took 0.8011116981506348s
Understandability | Number of label check for Japan Search took 4.750189781188965s
Understandability | URI regex check for Japan Search took 1.0356342792510986s
Understandability | Vocabs check for Japan Search took 0.7598896026611328s
Verifiability | Authors check for Japan Search took 0.3584587574005127s
Verifiability | Publishers check for Japan Search took 0.26184701919555664s
Performance | Throughput check for Japan Search took 11.3698890209198s
Amount of data | Check the number of entities for Japan Search took 8.20159912109375e-05s
Verifiability | Contribs. check for Japan Search took 0.2860124111175537s
Interlinking | sameAs chians check for Japan Search took 0.28819847106933594s
Interlinking | skos check for Japan Search took 0.3328437805175781s
Interlinking | skos check for Japan Search took 0.2909817695617676s
Timeliness | dataset update frequency check for Japan Search took 0.46674346923828125s
Currency | Creation date check for Japan Search took 1.2761390209197998s
Currency | Modification date check for Japan Search took 0.6000769138336182s
Rep.Conc. | URIs length for Japan Search took 30.11721706390381s
Interoperability | New vocabularies check for Japan Search took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.7361645698547363s
Accuracy | Check Empty annotation labels for Japan Search took 1.7888009548187256s
Accuracy | Check White space in annotation for Japan Search took 0.032047271728515625s
Accuracy | Check Datatype consistency for Japan Search took 0.03231477737426758s
Consistency | Disjoint class check for Japan Search took 0.28057003021240234s
Consistency | Check Misplaced properties for Japan Search took 26.626713752746582s
Consistency | Misplaced classes for Japan Search took 0.37869715690612793s
Consistency | Check Ontology hijacking for Japan Search took 2.6568431854248047s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.3651483058929443s
Consistency | Check Invalid usage of undefined properties for Japan Search took 27.85856032371521s
Conciseness | Check Extensional conciseness for Japan Search took 0.037313222885131836s
Conciseness | Check Intensional conciseness for Japan Search took 0.3771798610687256s
Security | Sign check for Japan Search took 0.3440737724304199s
Availability | Check URIs Dereferenciability for Japan Search took 8.794559717178345s
Completeness | Calculation of interlinking completeness for Japan Search took 0.7159538269042969s
Reputation | Calculation of the PageRank for Japan Search took 0.021115541458129883s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Japan Search took 2.09808349609375e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 1.1920928955078125e-06s
Believability | Calculation of trust value for Japan Search took 1.430511474609375e-05s
INFO | --- Analysis for Japan-Search took 660.0633428096771s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.1503465175628662s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.29866456985473633s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.021254777908325195s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.5735626220703125e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.0728836059570312e-05s
INFO | --- Analysis for Rijksmuseum took 5.1684582233428955s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.9289073944091797s
Availability | VoID file availability check for Finnish Public Libraries took 0.0006718635559082031s
Extra | Recovery of all triples for Finnish Public Libraries took 81.40441918373108s
Performance | Total latancy measurement for Finnish Public Libraries took 1.299837350845337s
Amount of data | Number of triples check for Finnish Public Libraries took 100.08923721313477s
Versatility | Languages check for Finnish Public Libraries took 89.15572905540466s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 102.64739346504211s
Interpretability | RDF structures check for Finnish Public Libraries took 46.311729431152344s
Versatility | Serialization formats check for Finnish Public Libraries took 0.11750650405883789s
Availability | RDF dump link check for Finnish Public Libraries took 0.2639901638031006s
License | MR license check for Finnish Public Libraries took 0.30789804458618164s
License | HR license check for Finnish Public Libraries took 0.13136720657348633s
Amount of data | Number of property check for Finnish Public Libraries took 0.28026819229125977s
Understandability | Number of label check for Finnish Public Libraries took 0.12807869911193848s
Understandability | URI regex check for Finnish Public Libraries took 0.4052278995513916s
Understandability | Vocabs check for Finnish Public Libraries took 0.10660386085510254s
Verifiability | Authors check for Finnish Public Libraries took 0.2819342613220215s
Verifiability | Publishers check for Finnish Public Libraries took 0.20702123641967773s
Amount of data | Check the number of entities for Finnish Public Libraries took 6.937980651855469e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.10830426216125488s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.1334998607635498s
Interlinking | skos check for Finnish Public Libraries took 0.20439410209655762s
Interlinking | skos check for Finnish Public Libraries took 0.21168208122253418s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.11217856407165527s
Currency | Creation date check for Finnish Public Libraries took 0.3737912178039551s
Currency | Modification date check for Finnish Public Libraries took 0.4552309513092041s
Rep.Conc. | URIs length for Finnish Public Libraries took 0.2851731777191162s
Interoperability | New vocabularies check for Finnish Public Libraries took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.12203240394592285s
Consistency | Disjoint class check for Finnish Public Libraries took 0.12015056610107422s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 0.26610493659973145s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 1.502239465713501s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 0.00016307830810546875s
Security | Sign check for Finnish Public Libraries took 0.15003037452697754s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.4223935604095459s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.02312016487121582s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.8358230590820312e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 7.152557373046875e-07s
Believability | Calculation of trust value for Finnish Public Libraries took 1.4781951904296875e-05s
INFO | --- Analysis for FI-Library took 536.4022281169891s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 2.4142191410064697s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.000301361083984375s
Extra | Recovery of all triples for Shanghai Library Open Data Platform took 11.10914659500122s
Performance | Total latancy measurement for Shanghai Library Open Data Platform took 3.645930528640747s
Amount of data | Number of triples check for Shanghai Library Open Data Platform took 1.112898826599121s
Interoperability | New terms check for Shanghai Library Open Data Platform took 4.649555921554565s
Versatility | Languages check for Shanghai Library Open Data Platform took 60.77681112289429s
Interpretability | Number of blank nodes check for Shanghai Library Open Data Platform took 16.66496992111206s
Interpretability | RDF structures check for Shanghai Library Open Data Platform took 1.1495563983917236s
Versatility | Serialization formats check for Shanghai Library Open Data Platform took 0.8727269172668457s
Availability | RDF dump link check for Shanghai Library Open Data Platform took 0.7690956592559814s
License | MR license check for Shanghai Library Open Data Platform took 1.1128599643707275s
License | HR license check for Shanghai Library Open Data Platform took 36.62881398200989s
Amount of data | Number of property check for Shanghai Library Open Data Platform took 0.7177870273590088s
Understandability | Number of label check for Shanghai Library Open Data Platform took 1.3985121250152588s
Understandability | URI regex check for Shanghai Library Open Data Platform took 1.5794157981872559s
Understandability | Vocabs check for Shanghai Library Open Data Platform took 0.7703676223754883s
Verifiability | Authors check for Shanghai Library Open Data Platform took 0.9201450347900391s
Verifiability | Publishers check for Shanghai Library Open Data Platform took 0.8120794296264648s
Performance | Throughput check for Shanghai Library Open Data Platform took 14.318317890167236s
Amount of data | Check the number of entities for Shanghai Library Open Data Platform took 7.367134094238281e-05s
Verifiability | Contribs. check for Shanghai Library Open Data Platform took 0.746049165725708s
Interlinking | sameAs chians check for Shanghai Library Open Data Platform took 0.7475817203521729s
Interlinking | skos check for Shanghai Library Open Data Platform took 1.164769172668457s
Interlinking | skos check for Shanghai Library Open Data Platform took 0.731403112411499s
Timeliness | dataset update frequency check for Shanghai Library Open Data Platform took 0.9032251834869385s
Currency | Creation date check for Shanghai Library Open Data Platform took 1.4997920989990234s
Currency | Modification date check for Shanghai Library Open Data Platform took 1.522829294204712s
Rep.Conc. | URIs length for Shanghai Library Open Data Platform took 9.90639615058899s
Interoperability | New vocabularies check for Shanghai Library Open Data Platform took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for Shanghai Library Open Data Platform took 0.7152292728424072s
Accuracy | Check Functional Property for Shanghai Library Open Data Platform took 0.759103536605835s
Accuracy | Check Inverse Functional Property for Shanghai Library Open Data Platform took 0.7665448188781738s
Accuracy | Check Empty annotation labels for Shanghai Library Open Data Platform took 3.764227867126465s
Accuracy | Check White space in annotation for Shanghai Library Open Data Platform took 0.15250825881958008s
Accuracy | Check Datatype consistency for Shanghai Library Open Data Platform took 0.14584040641784668s
Consistency | Disjoint class check for Shanghai Library Open Data Platform took 0.8778882026672363s
Consistency | Check Misplaced properties for Shanghai Library Open Data Platform took 6.317859888076782s
Consistency | Misplaced classes for Shanghai Library Open Data Platform took 1.357055425643921s
Consistency | Check Ontology hijacking for Shanghai Library Open Data Platform took 4.562435626983643s
Consistency | Check Invalid usage of undefined classes for Shanghai Library Open Data Platform took 1.3524272441864014s
Consistency | Check Invalid usage of undefined properties for Shanghai Library Open Data Platform took 7.038205862045288s
Conciseness | Check Extensional conciseness for Shanghai Library Open Data Platform took 0.1486055850982666s
Conciseness | Check Intensional conciseness for Shanghai Library Open Data Platform took 1.2039783000946045s
Security | Sign check for Shanghai Library Open Data Platform took 1.1339566707611084s
Availability | Check URIs Dereferenciability for Shanghai Library Open Data Platform took 10.3398916721344s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.34219980239868164s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.021216392517089844s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 2.4080276489257812e-05s
Interoperability | Check the re-using of existing vocabs for Shanghai Library Open Data Platform took 2.1457672119140625e-06s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 1.0013580322265625e-05s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 348.9017391204834s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.3525867462158203s
Availability | VoID file availability check for National Library Netherlands took 0.0007083415985107422s
Extra | Recovery of all triples for National Library Netherlands took 0.9836926460266113s
Performance | Total latancy measurement for National Library Netherlands took 0.7943141460418701s
Amount of data | Number of triples check for National Library Netherlands took 0.6287767887115479s
Interoperability | New terms check for National Library Netherlands took 2.205705165863037s
Versatility | Languages check for National Library Netherlands took 58.154019355773926s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.1752009391784668s
Interpretability | RDF structures check for National Library Netherlands took 0.4863471984863281s
Versatility | Serialization formats check for National Library Netherlands took 0.15395569801330566s
Availability | RDF dump link check for National Library Netherlands took 0.16553115844726562s
License | MR license check for National Library Netherlands took 0.17712950706481934s
License | HR license check for National Library Netherlands took 58.146146059036255s
Amount of data | Number of property check for National Library Netherlands took 0.14299321174621582s
Understandability | Number of label check for National Library Netherlands took 3.0215585231781006s
Understandability | URI regex check for National Library Netherlands took 1.1794371604919434s
Understandability | Vocabs check for National Library Netherlands took 0.4539976119995117s
Verifiability | Authors check for National Library Netherlands took 0.7092165946960449s
Verifiability | Publishers check for National Library Netherlands took 0.43813419342041016s
Performance | Throughput check for National Library Netherlands took 10.849922180175781s
Amount of data | Check the number of entities for National Library Netherlands took 0.00011682510375976562s
Verifiability | Contribs. check for National Library Netherlands took 0.28124523162841797s
Interlinking | sameAs chians check for National Library Netherlands took 0.2982308864593506s
Interlinking | skos check for National Library Netherlands took 0.49877238273620605s
Interlinking | skos check for National Library Netherlands took 0.14363980293273926s
Timeliness | dataset update frequency check for National Library Netherlands took 0.3736305236816406s
Currency | Creation date check for National Library Netherlands took 0.5151183605194092s
Currency | Modification date check for National Library Netherlands took 0.375443696975708s
Rep.Conc. | URIs length for National Library Netherlands took 4.945237874984741s
Interoperability | New vocabularies check for National Library Netherlands took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.19013547897338867s
Accuracy | Check Functional Property for National Library Netherlands took 0.2301628589630127s
Accuracy | Check Inverse Functional Property for National Library Netherlands took 0.22097277641296387s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.570054292678833s
Accuracy | Check White space in annotation for National Library Netherlands took 0.027525901794433594s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.028491973876953125s
Consistency | Disjoint class check for National Library Netherlands took 0.2498035430908203s
Consistency | Check Misplaced properties for National Library Netherlands took 3.6434011459350586s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.9087457656860352s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 1.3630516529083252s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.5324785709381104s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.0290682315826416s
Security | Sign check for National Library Netherlands took 0.5340490341186523s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1760.856925725937s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.7292113304138184s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.022236347198486328s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 2.4318695068359375e-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.4066696166992188e-05s
INFO | --- Analysis for National-Library-Netherlands took 1942.0811371803284s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.5139179229736328s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.3122732639312744s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.02176976203918457s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.52587890625e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.5020370483398438e-05s
INFO | --- Analysis for Antique-Renaissance took 6.356688499450684s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 4.0248167514801025s
Availability | VoID file availability check for ARTSDATA.CA took 0.0007724761962890625s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.2799854278564453s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.02186131477355957s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.6689300537109375e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 1.6689300537109375e-05s
INFO | --- Analysis for ARTSDATA-CA took 10.358126878738403s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.2459094524383545s
Availability | VoID file availability check for Architecture of Knowledge took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.34330058097839355s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.021456241607666016s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.5735626220703125e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 1.52587890625e-05s
INFO | --- Analysis for ArCo took 4.088435649871826s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.34433650970458984s
Availability | VoID file availability check for ConfermentSampo took 0.0005323886871337891s
Extra | Recovery of all triples for ConfermentSampo took 18.502908945083618s
Performance | Total latancy measurement for ConfermentSampo took 0.8401296138763428s
Amount of data | Number of triples check for ConfermentSampo took 8.16495680809021s
Interoperability | New terms check for ConfermentSampo took 2.8936634063720703s
Versatility | Languages check for ConfermentSampo took 24.884536027908325s
Interpretability | Number of blank nodes check for ConfermentSampo took 7.5034167766571045s
Security | Check HTTPS for ConfermentSampo took 0.3882925510406494s
Interpretability | RDF structures check for ConfermentSampo took 0.2348647117614746s
Versatility | Serialization formats check for ConfermentSampo took 0.22688961029052734s
Availability | RDF dump link check for ConfermentSampo took 3.173898935317993s
License | MR license check for ConfermentSampo took 0.21391940116882324s
License | HR license check for ConfermentSampo took 0.23436903953552246s
Amount of data | Number of property check for ConfermentSampo took 0.1902918815612793s
Understandability | Number of label check for ConfermentSampo took 5.192441701889038s
Understandability | URI regex check for ConfermentSampo took 0.3555171489715576s
Understandability | Vocabs check for ConfermentSampo took 0.1849384307861328s
Verifiability | Authors check for ConfermentSampo took 0.20029616355895996s
Verifiability | Publishers check for ConfermentSampo took 0.20036816596984863s
Performance | Throughput check for ConfermentSampo took 11.008010864257812s
Amount of data | Check the number of entities for ConfermentSampo took 4.301803350448608s
Verifiability | Contribs. check for ConfermentSampo took 0.1665022373199463s
Interlinking | sameAs chians check for ConfermentSampo took 0.3959214687347412s
Interlinking | skos check for ConfermentSampo took 0.1748957633972168s
Interlinking | skos check for ConfermentSampo took 0.15009784698486328s
Timeliness | dataset update frequency check for ConfermentSampo took 0.16252374649047852s
Currency | Creation date check for ConfermentSampo took 0.34743261337280273s
Currency | Modification date check for ConfermentSampo took 0.3773813247680664s
Rep.Conc. | URIs length for ConfermentSampo took 34.382962226867676s
Interoperability | New vocabularies check for ConfermentSampo took 1.1920928955078125e-05s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.198899507522583s
Accuracy | Check Functional Property for ConfermentSampo took 0.19605612754821777s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.16364145278930664s
Accuracy | Check Empty annotation labels for ConfermentSampo took 15.543042659759521s
Accuracy | Check White space in annotation for ConfermentSampo took 3.041443109512329s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.316577196121216s
Consistency | Disjoint class check for ConfermentSampo took 0.18586039543151855s
Consistency | Check Misplaced properties for ConfermentSampo took 6.557622194290161s
Consistency | Check Ontology hijacking for ConfermentSampo took 15.396138191223145s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.5626823902130127s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.6744282245635986s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.8758251667022705s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.2010338306427002s
Security | Sign check for ConfermentSampo took 0.16415023803710938s
Availability | Check URIs Dereferenciability for ConfermentSampo took 1479.6817607879639s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 6.018889665603638s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.0220797061920166s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 6.103515625e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 1.6689300537109375e-06s
Believability | Calculation of trust value for ConfermentSampo took 1.621246337890625e-05s
INFO | --- Analysis for ConfermentSampo took 1779.8161573410034s
Availability | SPARQL endpoint availability check for Museum Finland took 0.3457932472229004s
Availability | VoID file availability check for Museum Finland took 0.0005826950073242188s
Extra | Recovery of all triples for Museum Finland took 4.686449289321899s
Performance | Total latancy measurement for Museum Finland took 0.830479621887207s
Amount of data | Number of triples check for Museum Finland took 0.3552718162536621s
Interoperability | New terms check for Museum Finland took 1.8776118755340576s
Versatility | Languages check for Museum Finland took 0.6529495716094971s
Interpretability | Number of blank nodes check for Museum Finland took 0.32106661796569824s
Security | Check HTTPS for Museum Finland took 0.24176740646362305s
Interpretability | RDF structures check for Museum Finland took 0.4558243751525879s
Versatility | Serialization formats check for Museum Finland took 0.20403575897216797s
Availability | RDF dump link check for Museum Finland took 0.16838479042053223s
License | MR license check for Museum Finland took 0.18712973594665527s
License | HR license check for Museum Finland took 0.40872931480407715s
Amount of data | Number of property check for Museum Finland took 0.1976761817932129s
Understandability | Number of label check for Museum Finland took 0.2703287601470947s
Understandability | URI regex check for Museum Finland took 0.3120381832122803s
Understandability | Vocabs check for Museum Finland took 0.15294218063354492s
Verifiability | Authors check for Museum Finland took 0.15448880195617676s
Verifiability | Publishers check for Museum Finland took 0.16553139686584473s
Performance | Throughput check for Museum Finland took 11.217061519622803s
Amount of data | Check the number of entities for Museum Finland took 8.273124694824219e-05s
Verifiability | Contribs. check for Museum Finland took 0.16672062873840332s
Interlinking | sameAs chians check for Museum Finland took 0.1623685359954834s
Interlinking | skos check for Museum Finland took 0.16817712783813477s
Interlinking | skos check for Museum Finland took 0.16956877708435059s
Timeliness | dataset update frequency check for Museum Finland took 0.1539156436920166s
Currency | Creation date check for Museum Finland took 0.35773348808288574s
Currency | Modification date check for Museum Finland took 0.3747255802154541s
Rep.Conc. | URIs length for Museum Finland took 3.7114381790161133s
Interoperability | New vocabularies check for Museum Finland took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.1915597915649414s
Accuracy | Check Functional Property for Museum Finland took 0.15961289405822754s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.16798758506774902s
Accuracy | Check Empty annotation labels for Museum Finland took 1.0552105903625488s
Accuracy | Check White space in annotation for Museum Finland took 0.06241011619567871s
Accuracy | Check Datatype consistency for Museum Finland took 1.008173942565918s
Consistency | Disjoint class check for Museum Finland took 0.16820502281188965s
Consistency | Check Misplaced properties for Museum Finland took 0.6334781646728516s
Consistency | Check Ontology hijacking for Museum Finland took 2.403757333755493s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.704171895980835s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.8858544826507568s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6783015727996826s
Conciseness | Check Intensional conciseness for Museum Finland took 0.33162593841552734s
Security | Sign check for Museum Finland took 0.1520678997039795s
Availability | Check URIs Dereferenciability for Museum Finland took 2607.745022058487s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.7149159908294678s
Reputation | Calculation of the PageRank for Museum Finland took 0.022774219512939453s
Interlinking | Calculation of Degree of Connection for Museum Finland took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0008137226104736328s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 6.699562072753906e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 2.1457672119140625e-06s
Believability | Calculation of trust value for Museum Finland took 1.33514404296875e-05s
INFO | --- Analysis for FI-Museum took 2664.2517626285553s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.19073939323425293s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0006604194641113281s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 15.855787515640259s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.8243694305419922s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 29.62792134284973s
Interoperability | New terms check for Mapping Manuscript Migrations took 4.919039487838745s
Versatility | Languages check for Mapping Manuscript Migrations took 75.44458723068237s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 29.370107173919678s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.38826704025268555s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.19129371643066406s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.19182777404785156s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.16023683547973633s
License | MR license check for Mapping Manuscript Migrations took 0.19150733947753906s
License | HR license check for Mapping Manuscript Migrations took 1.8316967487335205s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.19701552391052246s
Understandability | Number of label check for Mapping Manuscript Migrations took 8.830771923065186s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.35121583938598633s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.1611626148223877s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.19863247871398926s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.1840674877166748s
Performance | Throughput check for Mapping Manuscript Migrations took 11.106432914733887s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.1758613586425781s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.16021990776062012s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.5100054740905762s
Interlinking | skos check for Mapping Manuscript Migrations took 0.1675124168395996s
Interlinking | skos check for Mapping Manuscript Migrations took 0.16793608665466309s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.16037368774414062s
Currency | Creation date check for Mapping Manuscript Migrations took 0.36675095558166504s
Currency | Modification date check for Mapping Manuscript Migrations took 0.1918482780456543s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 48.91645956039429s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.1538095474243164s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.15766406059265137s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.16674470901489258s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 11.17778730392456s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.465996742248535s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.914717197418213s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.19112443923950195s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 22.610870838165283s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 16.906033039093018s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.7161779403686523s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.695387601852417s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.8912253379821777s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.19879412651062012s
Security | Sign check for Mapping Manuscript Migrations took 0.1593790054321289s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1600.8043518066406s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.58089280128479s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.023281097412109375s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 6.4849853515625e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 2.384185791015625e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 1.621246337890625e-05s
INFO | --- Analysis for MMM took 2007.133805513382s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.19835543632507324s
Availability | VoID file availability check for Semantic Kalevala took 0.000537872314453125s
Extra | Recovery of all triples for Semantic Kalevala took 8.409564018249512s
Performance | Total latancy measurement for Semantic Kalevala took 0.8008849620819092s
Amount of data | Number of triples check for Semantic Kalevala took 0.4219391345977783s
Interoperability | New terms check for Semantic Kalevala took 3.0027871131896973s
Versatility | Languages check for Semantic Kalevala took 0.9522311687469482s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.38785552978515625s
Security | Check HTTPS for Semantic Kalevala took 0.3895566463470459s
Interpretability | RDF structures check for Semantic Kalevala took 0.6015148162841797s
Versatility | Serialization formats check for Semantic Kalevala took 0.19157910346984863s
Availability | RDF dump link check for Semantic Kalevala took 0.17395305633544922s
License | MR license check for Semantic Kalevala took 0.2812068462371826s
License | HR license check for Semantic Kalevala took 1.0317449569702148s
Amount of data | Number of property check for Semantic Kalevala took 0.1970996856689453s
Understandability | Number of label check for Semantic Kalevala took 0.8622052669525146s
Understandability | URI regex check for Semantic Kalevala took 0.3219902515411377s
Understandability | Vocabs check for Semantic Kalevala took 0.15276765823364258s
Verifiability | Authors check for Semantic Kalevala took 0.1605067253112793s
Verifiability | Publishers check for Semantic Kalevala took 0.15315914154052734s
Performance | Throughput check for Semantic Kalevala took 11.086082458496094s
Amount of data | Check the number of entities for Semantic Kalevala took 8.726119995117188e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.18439364433288574s
Interlinking | sameAs chians check for Semantic Kalevala took 0.20353245735168457s
Interlinking | skos check for Semantic Kalevala took 0.3426365852355957s
Interlinking | skos check for Semantic Kalevala took 0.15716814994812012s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.18993616104125977s
Currency | Creation date check for Semantic Kalevala took 0.3697957992553711s
Currency | Modification date check for Semantic Kalevala took 0.35990333557128906s
Rep.Conc. | URIs length for Semantic Kalevala took 5.170238733291626s
Interoperability | New vocabularies check for Semantic Kalevala took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.1933736801147461s
Accuracy | Check Functional Property for Semantic Kalevala took 0.19823718070983887s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.15908575057983398s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.877293348312378s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.30099964141845703s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.510345697402954s
Consistency | Disjoint class check for Semantic Kalevala took 0.1605391502380371s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.7878127098083496s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.5046021938323975s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.5573413372039795s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.7446680068969727s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.9132089614868164s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.29594874382019043s
Security | Sign check for Semantic Kalevala took 0.15316414833068848s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 2337.3747684955597s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.7190682888031006s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.6831345558166504s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 3.0279159545898438e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.7642974853515625e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 2.86102294921875e-06s
Believability | Calculation of trust value for Semantic Kalevala took 1.0251998901367188e-05s
INFO | --- Analysis for Semantic-Kalevala took 2424.56515789032s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 1.2414085865020752s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.000675201416015625s
Extra | Recovery of all triples for Smithsonian American Art Museum took 263.4298746585846s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.877570390701294s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5621726512908936s
Interoperability | New terms check for Smithsonian American Art Museum took 4.2942280769348145s
Versatility | Languages check for Smithsonian American Art Museum took 27.76708436012268s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.5735042095184326s
Security | Check HTTPS for Smithsonian American Art Museum took 0.36003661155700684s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.8380651473999023s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.593766450881958s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.6087722778320312s
License | MR license check for Smithsonian American Art Museum took 0.5810973644256592s
License | HR license check for Smithsonian American Art Museum took 17.222240924835205s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5898110866546631s
Understandability | Number of label check for Smithsonian American Art Museum took 0.5773477554321289s
Understandability | URI regex check for Smithsonian American Art Museum took 1.1582388877868652s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.619260311126709s
Verifiability | Authors check for Smithsonian American Art Museum took 0.61318039894104s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.567270040512085s
Performance | Throughput check for Smithsonian American Art Museum took 11.564024925231934s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 8.177757263183594e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.592233419418335s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.577467679977417s
Interlinking | skos check for Smithsonian American Art Museum took 0.5606329441070557s
Interlinking | skos check for Smithsonian American Art Museum took 0.6069347858428955s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.5664010047912598s
Currency | Creation date check for Smithsonian American Art Museum took 1.2059688568115234s
Currency | Modification date check for Smithsonian American Art Museum took 1.249831199645996s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 105.78763890266418s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.5802226066589355s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 19.425281286239624s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.5024580955505371s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.312913417816162s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.594127893447876s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 4.6884520053863525s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 95.4119164943695s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.8092477321624756s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 5.286795139312744s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.9385366439819336s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.5838124752044678s
Security | Sign check for Smithsonian American Art Museum took 0.577373743057251s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.231949329376221s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.512101411819458s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.021234750747680664s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.621246337890625e-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.5020370483398438e-05s
INFO | --- Analysis for Smithsonian took 684.9821116924286s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.21592926979064941s
Availability | VoID file availability check for Zeri Photo Archive took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.29896020889282227s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.021715879440307617s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.5497207641601562e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 1.430511474609375e-05s
INFO | --- Analysis for Zeri-Photo-Archive took 6.530334711074829s
Availability | SPARQL endpoint availability check for Archives Hub took 20.4843327999115s
Availability | VoID file availability check for Archives Hub took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.30941104888916016s
Reputation | Calculation of the PageRank for Archives Hub took 0.021107196807861328s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.5974044799804688e-05s
Believability | Calculation of trust value for Archives Hub took 1.3828277587890625e-05s
INFO | --- Analysis for Archives-Hub took 57.948251485824585s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.729874610900879s
Availability | VoID file availability check for Yale centre of British Art took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.3387439250946045s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.02094888687133789s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.430511474609375e-05s
Believability | Calculation of trust value for Yale centre of British Art took 1.5735626220703125e-05s
INFO | --- Analysis for Yale took 5.431001663208008s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 262.86401987075806s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.28643798828125s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.022000551223754883s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.7881393432617188e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 1.52587890625e-05s
INFO | --- Analysis for ADL took 537.9555585384369s
Availability | SPARQL endpoint availability check for MusicKG took 0.652862548828125s
Availability | VoID file availability check for MusicKG took 0.0007355213165283203s
Completeness | Calculation of interlinking completeness for MusicKG took 0.31848859786987305s
Reputation | Calculation of the PageRank for MusicKG took 0.022247791290283203s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.52587890625e-05s
Believability | Calculation of trust value for MusicKG took 1.3589859008789062e-05s
INFO | --- Analysis for MusicKG took 4.7432756423950195s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 1.055248498916626s
Availability | VoID file availability check for CIDOC-CRM took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.311093807220459s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.0210418701171875s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.4066696166992188e-05s
Believability | Calculation of trust value for CIDOC-CRM took 1.4781951904296875e-05s
INFO | --- Analysis for CIDOC-CRM took 5.585721015930176s
Availability | SPARQL endpoint availability check for Mondis took 10.408819913864136s
Availability | VoID file availability check for Mondis took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for Mondis took 0.30202198028564453s
Reputation | Calculation of the PageRank for Mondis took 0.022526979446411133s
Interlinking | Calculation of Degree of Connection for Mondis took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.33514404296875e-05s
Believability | Calculation of trust value for Mondis took 1.9073486328125e-05s
INFO | --- Analysis for Mondis took 14.263613939285278s
Availability | SPARQL endpoint availability check for DigitalNZ took 3.683544874191284s
Availability | VoID file availability check for DigitalNZ took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.355358362197876s
Reputation | Calculation of the PageRank for DigitalNZ took 0.024535179138183594s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.52587890625e-05s
Believability | Calculation of trust value for DigitalNZ took 1.3113021850585938e-05s
INFO | --- Analysis for DigitalNZ took 8.6786949634552s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.16279363632202148s
Availability | VoID file availability check for Fondazione Zeri took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.3287312984466553s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.020936965942382812s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.5735626220703125e-05s
Believability | Calculation of trust value for Fondazione Zeri took 1.1444091796875e-05s
INFO | --- Analysis for Fondazione-Zeri took 3.787647008895874s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.1941843032836914s
Availability | VoID file availability check for Digital Public Library of America took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.3286561965942383s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.0208280086517334s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.5974044799804688e-05s
Believability | Calculation of trust value for Digital Public Library of America took 1.2874603271484375e-05s
INFO | --- Analysis for Library-of-America took 5.061230897903442s
Availability | SPARQL endpoint availability check for Auckland Museum took 1.4251856803894043s
Availability | VoID file availability check for Auckland Museum took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.3278651237487793s
Reputation | Calculation of the PageRank for Auckland Museum took 0.020977020263671875s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.4543533325195312e-05s
Believability | Calculation of trust value for Auckland Museum took 1.430511474609375e-05s
INFO | --- Analysis for Auckland-Museum took 11.601210117340088s
Availability | SPARQL endpoint availability check for National Library of Spain took 6.2362682819366455s
Availability | VoID file availability check for National Library of Spain took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.3321666717529297s
Reputation | Calculation of the PageRank for National Library of Spain took 0.021136760711669922s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 2.002716064453125e-05s
Believability | Calculation of trust value for National Library of Spain took 1.4543533325195312e-05s
INFO | --- Analysis for BNE took 9.813683986663818s
Availability | SPARQL endpoint availability check for National Library of Korea took 2.395244598388672s
Availability | VoID file availability check for National Library of Korea took 0.00033211708068847656s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.3364248275756836s
Reputation | Calculation of the PageRank for National Library of Korea took 0.02094125747680664s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.52587890625e-05s
Believability | Calculation of trust value for National Library of Korea took 1.049041748046875e-05s
INFO | --- Analysis for Korea-Library took 6.084738731384277s
Availability | SPARQL endpoint availability check for The State Russian Museum took 1.5443742275238037s
Availability | VoID file availability check for The State Russian Museum took 0.0017042160034179688s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.3051173686981201s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.02146148681640625s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.4543533325195312e-05s
Believability | Calculation of trust value for The State Russian Museum took 1.52587890625e-05s
INFO | --- Analysis for Russian-Museum took 5.476099491119385s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.425440788269043s
Availability | VoID file availability check for National Library of Scotland took 0.0004138946533203125s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.3176741600036621s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.021300315856933594s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.6689300537109375e-05s
Believability | Calculation of trust value for National Library of Scotland took 1.0013580322265625e-05s
INFO | --- Analysis for National-Library-of-Scotland took 14.267126083374023s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.4077789783477783s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0007474422454833984s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.3381047248840332s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.021610021591186523s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0008251667022705078s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.6450881958007812e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 1.2636184692382812e-05s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 5.034243822097778s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.20317959785461426s
Availability | VoID file availability check for OntoComedySources took 0.00040030479431152344s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.3179304599761963s
Reputation | Calculation of the PageRank for OntoComedySources took 0.020907163619995117s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.430511474609375e-05s
Believability | Calculation of trust value for OntoComedySources took 1.5497207641601562e-05s
INFO | --- Analysis for OntoComedySources took 4.381482124328613s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.18036842346191406s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.5475780963897705s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.02244734764099121s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0008895397186279297s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.5735626220703125e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 1.5497207641601562e-05s
INFO | --- Analysis for OntoCeramic-2.0 took 5.212274789810181s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.11494946479797363s
Availability | VoID file availability check for SaintGall Ontology took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.3675675392150879s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.020812034606933594s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.4543533325195312e-05s
Believability | Calculation of trust value for SaintGall Ontology took 1.4543533325195312e-05s
INFO | --- Analysis for SaintGall-Ontology took 3.7062675952911377s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.8326413631439209s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.3163161277770996s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.021014690399169922s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.5497207641601562e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 1.5020370483398438e-05s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 6.588212013244629s
Availability | SPARQL endpoint availability check for ICON took 0.2534480094909668s
Availability | VoID file availability check for ICON took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for ICON took 0.2891409397125244s
Reputation | Calculation of the PageRank for ICON took 0.022016525268554688s
Interlinking | Calculation of Degree of Connection for ICON took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for ICON took 0.0010056495666503906s
Interlinking | Calculation of Clustering coefficient for ICON took 1.5735626220703125e-05s
Believability | Calculation of trust value for ICON took 1.5020370483398438e-05s
INFO | --- Analysis for ICON took 5.292695760726929s
Availability | SPARQL endpoint availability check for Polifonia took 0.29095959663391113s
Availability | VoID file availability check for Polifonia took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for Polifonia took 0.3238866329193115s
Reputation | Calculation of the PageRank for Polifonia took 0.02098250389099121s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.5497207641601562e-05s
Believability | Calculation of trust value for Polifonia took 1.430511474609375e-05s
INFO | --- Analysis for Polifonia took 5.089902400970459s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.24819040298461914s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.33401989936828613s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.02230072021484375s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.5020370483398438e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 1.5020370483398438e-05s
INFO | --- Analysis for Atlas-of-Paths took 4.497642993927002s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.20280075073242188s
Availability | VoID file availability check for Music Note Ontology took 0.0013544559478759766s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.3752148151397705s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.02177143096923828s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.5974044799804688e-05s
Believability | Calculation of trust value for Music Note Ontology took 1.4543533325195312e-05s
INFO | --- Analysis for Music-Note-Ontology took 8.971070766448975s
Availability | SPARQL endpoint availability check for HaMSE took 0.2004079818725586s
Availability | VoID file availability check for HaMSE took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for HaMSE took 0.31549811363220215s
Reputation | Calculation of the PageRank for HaMSE took 0.021051645278930664s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.5974044799804688e-05s
Believability | Calculation of trust value for HaMSE took 1.4543533325195312e-05s
INFO | --- Analysis for HaMSE took 5.385231971740723s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.1093292236328125s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0007932186126708984s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.3747262954711914s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.02120375633239746s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.4066696166992188e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 1.3589859008789062e-05s
INFO | --- Analysis for FOod took 5.619489908218384s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 1.575178623199463s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.33796024322509766s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.021867036819458008s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0008082389831542969s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.6450881958007812e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 1.4781951904296875e-05s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 9.020910024642944s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.3894829750061035s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.32194089889526367s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.021155834197998047s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.5020370483398438e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 1.4781951904296875e-05s
INFO | --- Analysis for ARIADNE took 6.1072447299957275s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.3010697364807129s
Availability | VoID file availability check for Odeuropa Ontology took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.46895694732666016s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.022884368896484375s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.6689300537109375e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 1.049041748046875e-05s
INFO | --- Analysis for Odeuropa took 3.9941232204437256s

--- Total time for analysis:851183.792331934s ---
--- Total time for analysis:236.4399423144261 hours ---