Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 9.298324584960938e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0008947849273681641s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.2688775062561035s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.523749828338623s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.0005764961242675781s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.1920928955078125e-05s
INFO | --- Analysis for 0080-3626 took 5.068788051605225s
Availability | SPARQL endpoint availability check for 土地利用图 took 7.605552673339844e-05s
Availability | VoID file availability check for 土地利用图 took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.3381218910217285s
Reputation | Calculation of the PageRank for 土地利用图 took 0.021793603897094727s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 4.5299530029296875e-05s
Believability | Calculation of trust value for 土地利用图 took 1.6689300537109375e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 2.756943464279175s
Availability | SPARQL endpoint availability check for 113322 took 7.05718994140625e-05s
Availability | VoID file availability check for 113322 took 0.0007824897766113281s
Completeness | Calculation of interlinking completeness for 113322 took 0.2935163974761963s
Reputation | Calculation of the PageRank for 113322 took 0.022461414337158203s
Interlinking | Calculation of Degree of Connection for 113322 took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for 113322 took 3.933906555175781e-05s
Believability | Calculation of trust value for 113322 took 1.5735626220703125e-05s
INFO | --- Analysis for 11 took 4.480315208435059s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 9.1552734375e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.28676271438598633s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.020856857299804688s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.9577484130859375e-05s
Believability | Calculation of trust value for Korepetycje Buki took 8.58306884765625e-06s
INFO | --- Analysis for 12323 took 2.653424024581909s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0680992603302002s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.31439661979675293s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020712852478027344s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 9.393692016601562e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 5.245208740234375e-06s
INFO | --- Analysis for 2000-us-census-rdf took 2.692157506942749s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.0943117141723633s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.30939674377441406s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.029273986816406e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 9.775161743164062e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 5.558127403259277s
Availability | SPARQL endpoint availability check for Open Data Web took 17.50898575782776s
Availability | VoID file availability check for Open Data Web took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.2741408348083496s
Reputation | Calculation of the PageRank for Open Data Web took 0.021807193756103516s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.218650817871094e-05s
Believability | Calculation of trust value for Open Data Web took 1.3589859008789062e-05s
INFO | --- Analysis for _data.odw.tw took 27.086299657821655s
Availability | SPARQL endpoint availability check for 土地利用 took 4.482269287109375e-05s
Availability | VoID file availability check for 土地利用 took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.303494930267334s
Reputation | Calculation of the PageRank for 土地利用 took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for 土地利用 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.504753112792969e-05s
Believability | Calculation of trust value for 土地利用 took 1.1920928955078125e-05s
INFO | --- Analysis for _data1.odw.tw took 2.7655739784240723s
Availability | SPARQL endpoint availability check for 土地利用模型 took 9.202957153320312e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.2921102046966553s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020931243896484375s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.6702880859375e-05s
Believability | Calculation of trust value for 土地利用模型 took 6.9141387939453125e-06s
INFO | --- Analysis for _data2.odw.tw took 12.376860618591309s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.678436279296875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2813103199005127s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8848648071289062e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.198883056640625e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 4.089583873748779s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 8.940696716308594e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.2758455276489258s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 2.7418136596679688e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 6.67572021484375e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 3.3134169578552246s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.2438507080078125e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0003819465637207031s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.2872600555419922s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020157814025878906s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 2.7894973754882812e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 4.76837158203125e-06s
INFO | --- Analysis for A1 took 3.2001123428344727s
Availability | SPARQL endpoint availability check for SummerOlympics took 2.2586638927459717s
Availability | VoID file availability check for SummerOlympics took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.29805541038513184s
Reputation | Calculation of the PageRank for SummerOlympics took 0.02289748191833496s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.151199340820312e-05s
Believability | Calculation of trust value for SummerOlympics took 1.0967254638671875e-05s
INFO | --- Analysis for abc took 9.166364908218384s
Availability | SPARQL endpoint availability check for Test_m took 5.9604644775390625e-05s
Availability | VoID file availability check for Test_m took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Test_m took 0.3029465675354004s
Reputation | Calculation of the PageRank for Test_m took 0.02152729034423828s
Interlinking | Calculation of Degree of Connection for Test_m took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0008516311645507812s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.3855438232421875e-05s
Believability | Calculation of trust value for Test_m took 1.0728836059570312e-05s
INFO | --- Analysis for ABC took 2.662524700164795s
Availability | SPARQL endpoint availability check for my intro took 8.869171142578125e-05s
Availability | VoID file availability check for my intro took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for my intro took 0.31272459030151367s
Reputation | Calculation of the PageRank for my intro took 0.020940780639648438s
Interlinking | Calculation of Degree of Connection for my intro took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for my intro took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for my intro took 2.86102294921875e-05s
Believability | Calculation of trust value for my intro took 1.0728836059570312e-05s
INFO | --- Analysis for abhay_intro took 2.7668142318725586s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.09226465225219727s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.29230570793151855s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.022827863693237305s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 9.72747802734375e-05s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for abs-linked-data took 2.800633192062378s
Availability | SPARQL endpoint availability check for AcadOnto took 8.58306884765625e-05s
Availability | VoID file availability check for AcadOnto took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.27630114555358887s
Reputation | Calculation of the PageRank for AcadOnto took 0.020747661590576172s
Interlinking | Calculation of Degree of Connection for AcadOnto took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 2.6702880859375e-05s
Believability | Calculation of trust value for AcadOnto took 1.1444091796875e-05s
INFO | --- Analysis for acadonto took 3.1722569465637207s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.354371070861816s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0008487701416015625s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.32758522033691406s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.02548956871032715s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0009183883666992188s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 6.389617919921875e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 8.58306884765625e-06s
INFO | --- Analysis for acorn-sat took 36.34050703048706s
Availability | SPARQL endpoint availability check for Addgene took 8.7738037109375e-05s
Availability | VoID file availability check for Addgene took 0.0007581710815429688s
Completeness | Calculation of interlinking completeness for Addgene took 0.3061220645904541s
Reputation | Calculation of the PageRank for Addgene took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for Addgene took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.266334533691406e-05s
Believability | Calculation of trust value for Addgene took 1.0967254638671875e-05s
INFO | --- Analysis for addgene took 15.535603046417236s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 8.940696716308594e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.2987387180328369s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 8.702278137207031e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.0251998901367188e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 9.640315294265747s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.5362083911895752s
Availability | VoID file availability check for AEMET metereological dataset took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.3036825656890869s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.361701965332031e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 1.049041748046875e-05s
INFO | --- Analysis for aemet took 13.926563739776611s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.042593955993652344s
Availability | VoID file availability check for AgriNepalData took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.2850956916809082s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 6.747245788574219e-05s
Believability | Calculation of trust value for AgriNepalData took 7.152557373046875e-06s
INFO | --- Analysis for agrinepaldata took 2.69063401222229s
Availability | SPARQL endpoint availability check for AGRIS took 262.2917375564575s
Availability | VoID file availability check for AGRIS took 0.0012693405151367188s
Completeness | Calculation of interlinking completeness for AGRIS took 0.35837316513061523s
Reputation | Calculation of the PageRank for AGRIS took 0.0216062068939209s
Interlinking | Calculation of Degree of Connection for AGRIS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AGRIS took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.152557373046875e-05s
Believability | Calculation of trust value for AGRIS took 9.775161743164062e-06s
INFO | --- Analysis for agris took 551.4700684547424s
Availability | SPARQL endpoint availability check for AGROVOC took 0.17578554153442383s
Availability | VoID file availability check for AGROVOC took 0.0005242824554443359s
Extra | Recovery of all triples for AGROVOC took 32.14826822280884s
Performance | Total latancy measurement for AGROVOC took 0.4329984188079834s
Amount of data | Number of triples check for AGROVOC took 25.547972679138184s
Interoperability | New terms check for AGROVOC took 3.1579198837280273s
Versatility | Languages check for AGROVOC took 67.80194735527039s
Interpretability | Number of blank nodes check for AGROVOC took 50.7735321521759s
Interpretability | RDF structures check for AGROVOC took 0.09846305847167969s
Versatility | Serialization formats check for AGROVOC took 0.0901496410369873s
Availability | RDF dump link check for AGROVOC took 0.08992290496826172s
License | MR license check for AGROVOC took 0.1114339828491211s
License | HR license check for AGROVOC took 0.5707008838653564s
Amount of data | Number of property check for AGROVOC took 0.0992133617401123s
Understandability | Number of label check for AGROVOC took 44.93444895744324s
Understandability | URI regex check for AGROVOC took 0.16195464134216309s
Understandability | Vocabs check for AGROVOC took 0.07792901992797852s
Verifiability | Authors check for AGROVOC took 0.07801961898803711s
Verifiability | Publishers check for AGROVOC took 0.09103107452392578s
Performance | Throughput check for AGROVOC took 10.420955181121826s
Amount of data | Check the number of entities for AGROVOC took 7.43865966796875e-05s
Verifiability | Contribs. check for AGROVOC took 0.07364726066589355s
Interlinking | sameAs chians check for AGROVOC took 0.09042096138000488s
Interlinking | skos check for AGROVOC took 1.6111247539520264s
Interlinking | skos check for AGROVOC took 1.3187296390533447s
Timeliness | dataset update frequency check for AGROVOC took 0.13749408721923828s
Currency | Creation date check for AGROVOC took 0.22299575805664062s
Currency | Modification date check for AGROVOC took 0.18550777435302734s
Rep.Conc. | URIs length for AGROVOC took 162.2486355304718s
Interoperability | New vocabularies check for AGROVOC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 48.8795166015625s
Accuracy | Check Functional Property for AGROVOC took 3.283867359161377s
Accuracy | Check Inverse Functional Property for AGROVOC took 6.7361016273498535s
Accuracy | Check Empty annotation labels for AGROVOC took 17.582979679107666s
Accuracy | Check White space in annotation for AGROVOC took 2.975809335708618s
Accuracy | Check Datatype consistency for AGROVOC took 4.418533563613892s
Consistency | Disjoint class check for AGROVOC took 13.969624519348145s
Consistency | Check Misplaced properties for AGROVOC took 23.611456871032715s
Consistency | Check Ontology hijacking for AGROVOC took 52.95545291900635s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.5413579940795898s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 22.260322332382202s
Conciseness | Check Extensional conciseness for AGROVOC took 2.5324695110321045s
Conciseness | Check Intensional conciseness for AGROVOC took 0.11212801933288574s
Security | Sign check for AGROVOC took 0.07269597053527832s
Availability | Check URIs Dereferenciability for AGROVOC took 2477.453902721405s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.6414666175842285s
Reputation | Calculation of the PageRank for AGROVOC took 0.021199464797973633s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00012302398681640625s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.9073486328125e-06s
Believability | Calculation of trust value for AGROVOC took 1.049041748046875e-05s
INFO | --- Analysis for agrovoc took 3135.048026561737s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.708388090133667s
Availability | VoID file availability check for Analytics India Magazine took 0.0006177425384521484s
Extra | Recovery of all triples for Analytics India Magazine took 2.467362642288208s
Performance | Total latancy measurement for Analytics India Magazine took 1.2066009044647217s
Amount of data | Number of triples check for Analytics India Magazine took 1.0579626560211182s
Versatility | Languages check for Analytics India Magazine took 1.0519483089447021s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.0513153076171875s
Interpretability | RDF structures check for Analytics India Magazine took 1.4433929920196533s
Versatility | Serialization formats check for Analytics India Magazine took 1.1157512664794922s
Availability | RDF dump link check for Analytics India Magazine took 1.0902884006500244s
License | MR license check for Analytics India Magazine took 1.171694040298462s
License | HR license check for Analytics India Magazine took 1.1690027713775635s
Amount of data | Number of property check for Analytics India Magazine took 1.006345510482788s
Understandability | Number of label check for Analytics India Magazine took 1.213296890258789s
Understandability | URI regex check for Analytics India Magazine took 2.0735228061676025s
Understandability | Vocabs check for Analytics India Magazine took 1.1712603569030762s
Verifiability | Authors check for Analytics India Magazine took 1.7679672241210938s
Verifiability | Publishers check for Analytics India Magazine took 1.4340541362762451s
Performance | Throughput check for Analytics India Magazine took 16.364746570587158s
Amount of data | Check the number of entities for Analytics India Magazine took 4.863739013671875e-05s
Verifiability | Contribs. check for Analytics India Magazine took 0.9516949653625488s
Interlinking | sameAs chians check for Analytics India Magazine took 1.0947084426879883s
Interlinking | skos check for Analytics India Magazine took 0.931736946105957s
Interlinking | skos check for Analytics India Magazine took 0.13318324089050293s
Timeliness | dataset update frequency check for Analytics India Magazine took 1.1397407054901123s
Currency | Creation date check for Analytics India Magazine took 2.239945411682129s
Currency | Modification date check for Analytics India Magazine took 2.3171074390411377s
Rep.Conc. | URIs length for Analytics India Magazine took 2.1936190128326416s
Interoperability | New vocabularies check for Analytics India Magazine took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 1.026033639907837s
Consistency | Disjoint class check for Analytics India Magazine took 1.003904104232788s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.0920138359069824s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 2.811396598815918s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.00020170211791992188s
Security | Sign check for Analytics India Magazine took 1.636486530303955s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.3031895160675049s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.02045464515686035s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0006837844848632812s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.147125244140625e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 1.1920928955078125e-06s
Believability | Calculation of trust value for Analytics India Magazine took 1.0251998901367188e-05s
INFO | --- Analysis for AIM took 92.61394834518433s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 9.012222290039062e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.298720121383667s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.02319812774658203s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.0040740966796875e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.049041748046875e-05s
INFO | --- Analysis for AISHE took 2.700444221496582s
Availability | SPARQL endpoint availability check for  equipment ontology took 0.00021767616271972656s
Availability | VoID file availability check for  equipment ontology took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.30438995361328125s
Reputation | Calculation of the PageRank for  equipment ontology took 0.020737648010253906s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for  equipment ontology took 1.0967254638671875e-05s
INFO | --- Analysis for akash took 2.6365416049957275s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 262.15509605407715s
Availability | VoID file availability check for aliada-scanbit-net took 0.0007777214050292969s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.3907756805419922s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020706892013549805s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00011539459228515625s
Believability | Calculation of trust value for aliada-scanbit-net took 1.1205673217773438e-05s
INFO | --- Analysis for aliada-scanbit-net took 1451.6563248634338s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.8570737838745117s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006213188171386719s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 137.30742263793945s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.812856435775757s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.435157060623169s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.8613221645355225s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.0560529232025s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.6407864093780518s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8816156387329102s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.8327946662902832s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.6358308792114258s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.6844089031219482s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.5752339363098145s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 31.17178964614868s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.58146071434021s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.7465147972106934s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1606557369232178s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.575716495513916s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6202375888824463s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5849933624267578s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.7952561378479s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 7.033348083496094e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5424652099609375s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5935077667236328s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5737729072570801s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6470017433166504s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.5791895389556885s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.1963460445404053s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.110231876373291s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 55.26369643211365s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 1.636432409286499s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5583570003509521s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6393435001373291s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6329257488250732s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 35.387988328933716s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.0033977031707764s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.5200412273406982s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.6158037185668945s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.604737281799316s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.602667570114136s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 33.62196493148804s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.3685798645019531s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.415615558624268s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.7544894218444824s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8550450801849365s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.7594718933105469s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 12706.344934463501s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.55063796043396s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.027706384658813477s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 8.368492126464844e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 4.525493860244751s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.1444091796875e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 13694.596867084503s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.2943308353424072s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.2631511688232422s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.838539123535156e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.239776611328125e-05s
INFO | --- Analysis for alpino-rdf took 3.5958242416381836s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.363059997558594e-05s
Availability | VoID file availability check for AAT-atawil took 0.0003292560577392578s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.2664198875427246s
Reputation | Calculation of the PageRank for AAT-atawil took 0.02169036865234375s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0010554790496826172s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.790855407714844e-05s
Believability | Calculation of trust value for AAT-atawil took 1.1682510375976562e-05s
INFO | --- Analysis for Altawil took 2.3806936740875244s
Availability | SPARQL endpoint availability check for Amer Nejma took 9.012222290039062e-05s
Availability | VoID file availability check for Amer Nejma took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.27116847038269043s
Reputation | Calculation of the PageRank for Amer Nejma took 0.02110600471496582s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.0994415283203125e-05s
Believability | Calculation of trust value for Amer Nejma took 5.9604644775390625e-06s
INFO | --- Analysis for Amer_Nejma took 2.3966102600097656s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.6534459590911865s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.26014018058776855s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.02205491065979004s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 8.654594421386719e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.298324584960938e-06s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.6382088661193848s
Availability | SPARQL endpoint availability check for Anime Dataset took 8.630752563476562e-05s
Availability | VoID file availability check for Anime Dataset took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.2647111415863037s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 2.765655517578125e-05s
Believability | Calculation of trust value for Anime Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for Anime took 3.329854965209961s
Availability | SPARQL endpoint availability check for ANNO took 9.441375732421875e-05s
Availability | VoID file availability check for ANNO took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for ANNO took 0.2686433792114258s
Reputation | Calculation of the PageRank for ANNO took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for ANNO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ANNO took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.361701965332031e-05s
Believability | Calculation of trust value for ANNO took 1.0013580322265625e-05s
INFO | --- Analysis for anno took 7.182422637939453s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 8.606910705566406e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.26902174949645996s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.2479248046875e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 1.0967254638671875e-05s
INFO | --- Analysis for AntiqueCarsCollection took 2.933561325073242s
Availability | SPARQL endpoint availability check for apache took 9.083747863769531e-05s
Availability | VoID file availability check for apache took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for apache took 0.27405309677124023s
Reputation | Calculation of the PageRank for apache took 0.02044200897216797s
Interlinking | Calculation of Degree of Connection for apache took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for apache took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for apache took 5.459785461425781e-05s
Believability | Calculation of trust value for apache took 1.1444091796875e-05s
INFO | --- Analysis for apache took 3.178556203842163s
Availability | SPARQL endpoint availability check for Apertium RDF took 9.250640869140625e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.2603027820587158s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020740270614624023s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF took 9.775161743164062e-06s
INFO | --- Analysis for apertium-rdf took 7.389038562774658s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.2737112045288086s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020841360092163086s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 9.292622566223145s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 9.369850158691406e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.26409101486206055s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.02098989486694336s
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.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 5.1975250244140625e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 55.63067603111267s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.00037670135498046875s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.26529717445373535s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.02251720428466797s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 6.842613220214844e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.1444091796875e-05s
INFO | --- Analysis for apertium-rdf-en-es took 53.85088300704956s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 8.821487426757812e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.26219725608825684s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020653724670410156s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 5.459785461425781e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 56.199050188064575s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0003848075866699219s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.2675666809082031s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.02035236358642578s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 3.981590270996094e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.0013580322265625e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 9.95101809501648s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.2688417434692383s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.020841121673583984s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.1961669921875e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 30.570974826812744s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 8.702278137207031e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.30122804641723633s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.021030902862548828s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 33.42435550689697s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 8.869171142578125e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.27878761291503906s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020985841751098633s
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.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.744529724121094e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 32.569889068603516s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.696846008300781e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.000701904296875s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2711355686187744s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.02082228660583496s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-es-an took 9.655597925186157s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 8.726119995117188e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.2791867256164551s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 55.21449160575867s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 9.083747863769531e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.2704448699951172s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.021234750747680664s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 5.0067901611328125e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 27.938827514648438s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0006899833679199219s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.2650477886199951s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020728111267089844s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 11.00388479232788s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 9.036064147949219e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0006976127624511719s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.2661402225494385s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.02033257484436035s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.935264587402344e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 53.46994233131409s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 8.893013000488281e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.26433658599853516s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 6.246566772460938e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.0013580322265625e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 8.730166673660278s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 9.083747863769531e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.2698681354522705s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 54.86569285392761s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 5.7220458984375e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.27685093879699707s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 32.97201228141785s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 8.845329284667969e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.30823254585266113s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.02070474624633789s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.7206878662109375e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 32.564587116241455s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 9.012222290039062e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.2919166088104248s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 7.152557373046875e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.0728836059570312e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 35.403812408447266s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.553794860839844e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.2657458782196045s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.021009206771850586s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 56.70236396789551s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0007162094116210938s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.26429224014282227s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020467042922973633s
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.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 58.10705351829529s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.744529724121094e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.2877366542816162s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020903587341308594s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 5.3882598876953125e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 6.503215312957764s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 8.869171142578125e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.2674434185028076s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.022062063217163086s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.982948303222656e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 82.5571756362915s
Availability | SPARQL endpoint availability check for AragoDBpedia - aragon open data took 0.6342916488647461s
Availability | VoID file availability check for AragoDBpedia - aragon open data took 0.0005288124084472656s
Extra | Recovery of all triples for AragoDBpedia - aragon open data took 3.8622188568115234s
Performance | Total latancy measurement for AragoDBpedia - aragon open data took 1.7531633377075195s
Amount of data | Number of triples check for AragoDBpedia - aragon open data took 0.7268764972686768s
Interoperability | New terms check for AragoDBpedia - aragon open data took 2.1145505905151367s
Versatility | Languages check for AragoDBpedia - aragon open data took 60.46303868293762s
Interpretability | Number of blank nodes check for AragoDBpedia - aragon open data took 4.415024042129517s
Security | Check HTTPS for AragoDBpedia - aragon open data took 0.2379450798034668s
Interpretability | RDF structures check for AragoDBpedia - aragon open data took 0.7175877094268799s
Versatility | Serialization formats check for AragoDBpedia - aragon open data took 1.2572336196899414s
Availability | RDF dump link check for AragoDBpedia - aragon open data took 0.39217638969421387s
License | MR license check for AragoDBpedia - aragon open data took 0.6478002071380615s
License | HR license check for AragoDBpedia - aragon open data took 6.559516429901123s
Amount of data | Number of property check for AragoDBpedia - aragon open data took 0.3748741149902344s
Understandability | Number of label check for AragoDBpedia - aragon open data took 0.5365772247314453s
Understandability | URI regex check for AragoDBpedia - aragon open data took 0.8453662395477295s
Understandability | Vocabs check for AragoDBpedia - aragon open data took 0.4230072498321533s
Verifiability | Authors check for AragoDBpedia - aragon open data took 0.4917440414428711s
Verifiability | Publishers check for AragoDBpedia - aragon open data took 0.38434290885925293s
Performance | Throughput check for AragoDBpedia - aragon open data took 10.506763458251953s
Amount of data | Check the number of entities for AragoDBpedia - aragon open data took 7.534027099609375e-05s
Verifiability | Contribs. check for AragoDBpedia - aragon open data took 0.4812631607055664s
Interlinking | sameAs chians check for AragoDBpedia - aragon open data took 0.4223144054412842s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.6107864379882812s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.3505401611328125s
Timeliness | dataset update frequency check for AragoDBpedia - aragon open data took 0.47335171699523926s
Currency | Creation date check for AragoDBpedia - aragon open data took 1.1574702262878418s
Currency | Modification date check for AragoDBpedia - aragon open data took 0.3849935531616211s
Rep.Conc. | URIs length for AragoDBpedia - aragon open data took 5.877887725830078s
Interoperability | New vocabularies check for AragoDBpedia - aragon open data took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for AragoDBpedia - aragon open data took 0.3723902702331543s
Accuracy | Check Functional Property for AragoDBpedia - aragon open data took 0.4177510738372803s
Accuracy | Check Inverse Functional Property for AragoDBpedia - aragon open data took 0.4264225959777832s
Accuracy | Check Empty annotation labels for AragoDBpedia - aragon open data took 1.1305842399597168s
Accuracy | Check White space in annotation for AragoDBpedia - aragon open data took 0.029708385467529297s
Accuracy | Check Datatype consistency for AragoDBpedia - aragon open data took 0.027890682220458984s
Consistency | Disjoint class check for AragoDBpedia - aragon open data took 0.37277770042419434s
Consistency | Check Misplaced properties for AragoDBpedia - aragon open data took 4.320427656173706s
Consistency | Misplaced classes for AragoDBpedia - aragon open data took 0.5887148380279541s
Consistency | Check Ontology hijacking for AragoDBpedia - aragon open data took 2.515507459640503s
Consistency | Check Invalid usage of undefined classes for AragoDBpedia - aragon open data took 1.349916696548462s
Consistency | Check Invalid usage of undefined properties for AragoDBpedia - aragon open data took 5.2915358543396s
Conciseness | Check Extensional conciseness for AragoDBpedia - aragon open data took 0.03440737724304199s
Conciseness | Check Intensional conciseness for AragoDBpedia - aragon open data took 0.5198497772216797s
Security | Sign check for AragoDBpedia - aragon open data took 0.5150737762451172s
Availability | Check URIs Dereferenciability for AragoDBpedia - aragon open data took 3075.2539279460907s
Completeness | Calculation of interlinking completeness for AragoDBpedia - aragon open data took 0.541633129119873s
Reputation | Calculation of the PageRank for AragoDBpedia - aragon open data took 0.021503448486328125s
Interlinking | Calculation of Degree of Connection for AragoDBpedia - aragon open data took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for AragoDBpedia - aragon open data took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for AragoDBpedia - aragon open data took 4.4345855712890625e-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 5.245208740234375e-06s
INFO | --- Analysis for aragodbpedia took 3340.924488544464s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.273402214050293s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.2685985565185547s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.02050304412841797s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.054473876953125e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for archiveshub-linkeddata took 83.01577496528625s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.865789890289307s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.26348018646240234s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.02026963233947754s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 2.7179718017578125e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 6.67572021484375e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 20.247809410095215s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.8484785556793213s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.27480387687683105s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.02105116844177246s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.838539123535156e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.1444091796875e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 16.70402979850769s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.3392181396484375e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.27246975898742676s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020923376083374023s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010132789611816406s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.1444091796875e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 9.073801517486572s
Availability | SPARQL endpoint availability check for Arthroscopy community took 5.53131103515625e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0003113746643066406s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.2568089962005615s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020860671997070312s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010085105895996094s
Believability | Calculation of trust value for Arthroscopy community took 7.3909759521484375e-06s
INFO | --- Analysis for arthroscopy took 12.470206260681152s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.9074647426605225s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0002815723419189453s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 26.48034691810608s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 65.15989804267883s
Interoperability | New terms check for Wikidata entry for Art × Science International took 1.9734632968902588s
Versatility | Languages check for Wikidata entry for Art × Science International took 60.176857233047485s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 65.3356339931488s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.366138219833374s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.15709447860717773s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.156541109085083s
License | MR license check for Wikidata entry for Art × Science International took 0.18129563331604004s
License | HR license check for Wikidata entry for Art × Science International took 65.16305613517761s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.6547863483428955s
Understandability | Number of label check for Wikidata entry for Art × Science International took 60.17391800880432s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.3142666816711426s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.18425774574279785s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.3309640884399414s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.19339990615844727s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 0.00015354156494140625s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.2042076587677002s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 0.15596652030944824s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.15616154670715332s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.181671142578125s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.15706133842468262s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.4013509750366211s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.4096410274505615s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 54.896737813949585s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.16774511337280273s
Accuracy | Check Empty annotation labels for Wikidata entry for Art × Science International took 15.217740058898926s
Accuracy | Check White space in annotation for Wikidata entry for Art × Science International took 2.6141862869262695s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.539958953857422s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.1984860897064209s
Consistency | Check Misplaced properties for Wikidata entry for Art × Science International took 25.641005992889404s
Consistency | Misplaced classes for Wikidata entry for Art × Science International took 8.64403223991394s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 28.537983417510986s
Consistency | Check Invalid usage of undefined classes for Wikidata entry for Art × Science International took 1.3727312088012695s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 9.332967758178711s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.7573094367980957s
Conciseness | Check Intensional conciseness for Wikidata entry for Art × Science International took 1.6035914421081543s
Security | Sign check for Wikidata entry for Art × Science International took 0.18764495849609375s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 8.899470329284668s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.33066296577453613s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.021175146102905273s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.7404556274414062e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 1.430511474609375e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 1.1920928955078125e-05s
INFO | --- Analysis for artxscienceinternational-wikidata took 943.8814218044281s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 10.230072736740112s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.26560282707214355s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.43865966796875e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 9.775161743164062e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 20.32901954650879s
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.658689498901367s
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.0006003379821777344s
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.2706873416900635s
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.020502328872680664s
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.0728836059570312e-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.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.343292236328125e-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.1920928955078125e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 12.139110326766968s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.6586761474609375s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.2672412395477295s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 8.440017700195312e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 13.321765422821045s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.64884352684021s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.2727317810058594s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.021926164627075195s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 3.886222839355469e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.1444091796875e-05s
INFO | --- Analysis for ASCDC-CRB took 15.656848430633545s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.647892475128174s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0003402233123779297s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.26239967346191406s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020696401596069336s
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.0008420944213867188s
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 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 12.68011999130249s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.6504573822021484s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.2668888568878174s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.022089004516601562s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.24249267578125e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.1444091796875e-05s
INFO | --- Analysis for ASCDC-DQOT took 13.866378784179688s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.6514205932617188s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2658348083496094s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.486343383789062e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 13.885637044906616s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 4.322391986846924s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.2715928554534912s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020748376846313477s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.106231689453125e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.3113021850585938e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 17.309831380844116s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.6568257808685303s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007472038269042969s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.26839470863342285s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.022541284561157227s
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.1444091796875e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.626678466796875e-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.3828277587890625e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 12.764962911605835s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.6537511348724365s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.2630434036254883s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020625829696655273s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.030632019042969e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 9.775161743164062e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 12.732002973556519s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.267542123794556s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.2652287483215332s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.02116990089416504s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.696846008300781e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.239776611328125e-05s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 17.41546320915222s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.6475815773010254s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.27756381034851074s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.843971252441406e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 12.183542490005493s
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.65307354927063s
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.0005698204040527344s
Completeness | Calculation of interlinking completeness for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.27437615394592285s
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.021721363067626953s
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.239776611328125e-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.0007281303405761719s
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 8.368492126464844e-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.1920928955078125e-05s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 13.90663456916809s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.656049966812134s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.27796244621276855s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.38690185546875e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 1.049041748046875e-05s
INFO | --- Analysis for ASCDC_-_DNB took 12.112138271331787s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 9.012222290039062e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2700512409210205s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020688772201538086s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.365776062011719e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.049041748046875e-05s
INFO | --- Analysis for asit took 7.36050271987915s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.57763671875e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.27388453483581543s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.021747827529907227s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.00107574462890625s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 5.054473876953125e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.239776611328125e-05s
INFO | --- Analysis for asjp took 4.5289506912231445s
Availability | SPARQL endpoint availability check for ASN:US took 1.671034336090088s
Availability | VoID file availability check for ASN:US took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for ASN:US took 0.2727808952331543s
Reputation | Calculation of the PageRank for ASN:US took 0.020432472229003906s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.413459777832031e-05s
Believability | Calculation of trust value for ASN:US took 8.58306884765625e-06s
INFO | --- Analysis for asn-us took 11.549724340438843s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.744529724121094e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.2665214538574219s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.021414518356323242s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 2.956390380859375e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 8.58306884765625e-06s
INFO | --- Analysis for aspire-mmu took 4.124918460845947s
Availability | SPARQL endpoint availability check for associations took 4.291534423828125e-05s
Availability | VoID file availability check for associations took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for associations took 0.2617380619049072s
Reputation | Calculation of the PageRank for associations took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for associations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for associations took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for associations took 7.534027099609375e-05s
Believability | Calculation of trust value for associations took 1.2636184692382812e-05s
INFO | --- Analysis for associations took 6.900463104248047s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 8.678436279296875e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.2700004577636719s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.02088165283203125s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.7738037109375e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.1205673217773438e-05s
INFO | --- Analysis for athelia-rfid took 6.165588855743408s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.608900785446167s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0003647804260253906s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.2935340404510498s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0009284019470214844s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.91278076171875e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 6.4373016357421875e-06s
INFO | --- Analysis for AugustiniConfessiones took 3.9582104682922363s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.43409132957458496s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.260317325592041s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.726119995117188e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 6.4373016357421875e-06s
INFO | --- Analysis for austrian_ski_racers took 3.4724278450012207s
Availability | SPARQL endpoint availability check for AVsOnto took 4.172325134277344e-05s
Availability | VoID file availability check for AVsOnto took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.2785685062408447s
Reputation | Calculation of the PageRank for AVsOnto took 0.020859718322753906s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 2.9087066650390625e-05s
Believability | Calculation of trust value for AVsOnto took 1.0251998901367188e-05s
INFO | --- Analysis for AVsOnto took 3.1235861778259277s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.335038423538208s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0003933906555175781s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 168.01403975486755s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.447235107421875s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.04911398887634s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 252.29200673103333s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.04895544052124s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.03632497787476s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2109813690185547s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.25626444816589355s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16945385932922363s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09135222434997559s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 55.55211353302002s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0071659088135s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11673426628112793s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 218.04706048965454s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.29204273223876953s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12973737716674805s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09866619110107422s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09386229515075684s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.376370191574097s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.3855438232421875e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.08796572685241699s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.073117017746s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.19644403457641602s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12160062789916992s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1159822940826416s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2576010227203369s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2300713062286377s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 903.6229493618011s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.4082612991333008s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.99288034439087s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.144744634628296s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.70326566696167s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.25444507598876953s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.18777990341187s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 22.568705558776855s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.4654786586761475s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.4611568450928s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.747515916824341s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15092968940734863s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.996546745300293s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.7443974018096924s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021366596221923828s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.295608520507812e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6689300537109375e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.58306884765625e-06s
INFO | --- Analysis for b3kat took 4384.795261383057s
Availability | SPARQL endpoint availability check for BabelNet took 0.4879109859466553s
Availability | VoID file availability check for BabelNet took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for BabelNet took 0.26505351066589355s
Reputation | Calculation of the PageRank for BabelNet took 0.020889759063720703s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00015974044799804688s
Believability | Calculation of trust value for BabelNet took 1.0251998901367188e-05s
INFO | --- Analysis for babelnet took 4.184881925582886s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 5.5789947509765625e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.266326904296875s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.021030426025390625s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.075599670410156e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.0967254638671875e-05s
INFO | --- Analysis for Bacevicius.lt took 2.397977590560913s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.4019200801849365s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.27623462677001953s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.021106481552124023s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.482269287109375e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.0728836059570312e-05s
INFO | --- Analysis for bag took 4.030556917190552s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 1.4137029647827148s
Availability | VoID file availability check for 红色经典歌曲 took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2694087028503418s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.0040740966796875e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.049041748046875e-05s
INFO | --- Analysis for baixue took 3.825673818588257s
Availability | SPARQL endpoint availability check for baixue composer took 0.0001068115234375s
Availability | VoID file availability check for baixue composer took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for baixue composer took 0.2732272148132324s
Reputation | Calculation of the PageRank for baixue composer took 0.022423267364501953s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0011219978332519531s
Interlinking | Calculation of Clustering coefficient for baixue composer took 4.029273986816406e-05s
Believability | Calculation of trust value for baixue composer took 1.1444091796875e-05s
INFO | --- Analysis for baixue_composer took 3.3051934242248535s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.0001232624053955078s
Availability | VoID file availability check for 红色经典歌曲 took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2735939025878906s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.022174596786499023s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.0994415283203125e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 9.775161743164062e-06s
INFO | --- Analysis for baixue_imagery took 2.913168430328369s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.482269287109375e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0007598400115966797s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2683436870574951s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.021073102951049805s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.5762786865234375e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1682510375976562e-05s
INFO | --- Analysis for baixue_imagery1 took 3.745229959487915s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 9.059906005859375e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007424354553222656s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.2730288505554199s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.02095818519592285s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.100799560546875e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 9.059906005859375e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.1016383171081543s
Availability | SPARQL endpoint availability check for BBC Music took 0.4805908203125s
Availability | VoID file availability check for BBC Music took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for BBC Music took 0.26790809631347656s
Reputation | Calculation of the PageRank for BBC Music took 0.02170276641845703s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00012683868408203125s
Believability | Calculation of trust value for BBC Music took 1.0251998901367188e-05s
INFO | --- Analysis for bbc-music took 3.6363563537597656s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.24594402313232422s
Availability | VoID file availability check for BBC Programmes took 0.0003058910369873047s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.2691025733947754s
Reputation | Calculation of the PageRank for BBC Programmes took 0.02101588249206543s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010728836059570312s
Believability | Calculation of trust value for BBC Programmes took 9.298324584960938e-06s
INFO | --- Analysis for bbc-programmes took 10.297340154647827s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.36453676223754883s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.2730882167816162s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020453214645385742s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 9.703636169433594e-05s
Believability | Calculation of trust value for BBC Wildlife Finder took 9.298324584960938e-06s
INFO | --- Analysis for bbc-wildlife-finder took 9.16892385482788s
Availability | SPARQL endpoint availability check for BBOP took 4.315376281738281e-05s
Availability | VoID file availability check for BBOP took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for BBOP took 0.27272701263427734s
Reputation | Calculation of the PageRank for BBOP took 0.021506071090698242s
Interlinking | Calculation of Degree of Connection for BBOP took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.123283386230469e-05s
Believability | Calculation of trust value for BBOP took 1.049041748046875e-05s
INFO | --- Analysis for bbop-selected took 19.820539712905884s
Availability | SPARQL endpoint availability check for Bdgp took 1.0082817077636719s
Availability | VoID file availability check for Bdgp took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Bdgp took 0.26964497566223145s
Reputation | Calculation of the PageRank for Bdgp took 0.020836830139160156s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bdgp took 9.775161743164062e-06s
INFO | --- Analysis for bdgp took 4.53980827331543s
Availability | SPARQL endpoint availability check for Bendev Junior took 8.988380432128906e-05s
Availability | VoID file availability check for Bendev Junior took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.26296281814575195s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 2.9087066650390625e-05s
Believability | Calculation of trust value for Bendev Junior took 1.1682510375976562e-05s
INFO | --- Analysis for bendevoficial took 3.288996458053589s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 6.364596366882324s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.2682688236236572s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.02041935920715332s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.389617919921875e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 9.059906005859375e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 17.08962082862854s
Availability | SPARQL endpoint availability check for berlios took 8.96453857421875e-05s
Availability | VoID file availability check for berlios took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for berlios took 0.26741528511047363s
Reputation | Calculation of the PageRank for berlios took 0.021036863327026367s
Interlinking | Calculation of Degree of Connection for berlios took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for berlios took 8.630752563476562e-05s
Believability | Calculation of trust value for berlios took 1.0251998901367188e-05s
INFO | --- Analysis for berlios took 2.7193470001220703s
Availability | SPARQL endpoint availability check for Between Our Worlds took 4.1961669921875e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.3194587230682373s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.021244287490844727s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.723403930664062e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.0013580322265625e-05s
INFO | --- Analysis for betweenourworlds took 8.32546091079712s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.08591461181640625s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.26791906356811523s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.021049022674560547s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.821487426757812e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for bfs-linked-data took 2.6068954467773438s
Availability | SPARQL endpoint availability check for BibBase took 0.05000710487365723s
Availability | VoID file availability check for BibBase took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for BibBase took 0.3088042736053467s
Reputation | Calculation of the PageRank for BibBase took 0.022869586944580078s
Interlinking | Calculation of Degree of Connection for BibBase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.274482727050781e-05s
Believability | Calculation of trust value for BibBase took 1.2159347534179688e-05s
INFO | --- Analysis for bibbase took 2.525097370147705s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 8.869171142578125e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.2716982364654541s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020800352096557617s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 9.655952453613281e-05s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 9.775161743164062e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 7.897074460983276s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 8.7738037109375e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.2748241424560547s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.021355390548706055s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.822845458984375e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.1682510375976562e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 6.401099443435669s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 5.125999450683594e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.26915907859802246s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.021165132522583008s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.6716461181640625e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.049041748046875e-05s
INFO | --- Analysis for BibSonomy took 11.17090392112732s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 9.131431579589844e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0003821849822998047s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.2705409526824951s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020884037017822266s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.2901763916015625e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.2159347534179688e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 5.519170761108398s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 8.893013000488281e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.2807424068450928s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.02280402183532715s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.123283386230469e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.1682510375976562e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.651146411895752s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 2.0061354637145996s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0005986690521240234s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 57.67818212509155s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 146.5625877380371s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 60.112712383270264s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.23883843421936s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 39.58182239532471s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 40.89238119125366s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 36.291019439697266s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 33.309581995010376s
License | MR license check for Bio2RDF::Affymetrix took 52.208624839782715s
License | HR license check for Bio2RDF::Affymetrix took 60.111510038375854s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 2.911746025085449s
Understandability | Number of label check for Bio2RDF::Affymetrix took 19.206408739089966s
Understandability | URI regex check for Bio2RDF::Affymetrix took 79.15072703361511s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 31.30429434776306s
Verifiability | Authors check for Bio2RDF::Affymetrix took 15.330177783966064s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 2.44389271736145s
Performance | Throughput check for Bio2RDF::Affymetrix took 98.70081543922424s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 75.24685764312744s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.2728891372680664s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.2185683250427246s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.7101595401763916s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.18497562408447266s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.09799003601074219s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.23456120491027832s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.2115180492401123s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 109.76623249053955s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 10.903142213821411s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.2789013385772705s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 6.778856039047241s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8805720806121826s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6374826431274414s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.37340593338012695s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 64.75477933883667s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.206514358520508s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.488159656524658s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.3133409023284912s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.41134595870972s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.6915810108184814s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.28513455390930176s
Security | Sign check for Bio2RDF::Affymetrix took 0.10483932495117188s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 10.859567880630493s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.45618581771850586s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010156631469726562s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 901.5825822353363s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.4543533325195312e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 2497.1451942920685s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.46332859992980957s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0005514621734619141s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 18.450134992599487s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.131103515625s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 43.93883728981018s
Interoperability | New terms check for Bio2RDF::Biomodels took 41.79838275909424s
Versatility | Languages check for Bio2RDF::Biomodels took 60.22753167152405s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2469038963317871s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.14501142501831055s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 1.0235931873321533s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.28585314750671387s
Availability | RDF dump link check for Bio2RDF::Biomodels took 1.8483881950378418s
License | MR license check for Bio2RDF::Biomodels took 0.524519681930542s
License | HR license check for Bio2RDF::Biomodels took 60.228923320770264s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.23448729515075684s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.943650722503662s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5364532470703125s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.23575687408447266s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.24040794372558594s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.23944830894470215s
Performance | Throughput check for Bio2RDF::Biomodels took 11.464603185653687s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 73.22736811637878s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 2.011565685272217s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.34752774238586426s
Interlinking | skos check for Bio2RDF::Biomodels took 0.9680726528167725s
Interlinking | skos check for Bio2RDF::Biomodels took 0.3303496837615967s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2384319305419922s
Currency | Creation date check for Bio2RDF::Biomodels took 0.46639084815979004s
Currency | Modification date check for Bio2RDF::Biomodels took 0.46959757804870605s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 108.61071920394897s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 490.5829701423645s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.6878037452697754s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.2633521556854248s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.256547212600708s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 6.842658519744873s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.8960733413696289s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6366355419158936s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.4060549736022949s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 64.97541928291321s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.315814256668091s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.374139070510864s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.2656643390655518s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.545801401138306s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.6824588775634766s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.8614077568054199s
Security | Sign check for Bio2RDF::Biomodels took 0.2449953556060791s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 10.162589073181152s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.5041005611419678s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020814180374145508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.0001163482666015625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 498.65575766563416s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1989.8408133983612s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.4424598217010498s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0003082752227783203s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 19.451436281204224s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.1421465873718262s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 44.2536461353302s
Interoperability | New terms check for Bio2RDF::Bioportal took 41.66266441345215s
Versatility | Languages check for Bio2RDF::Bioportal took 60.226799964904785s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.24760675430297852s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.14357995986938477s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.6547145843505859s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.2886776924133301s
Availability | RDF dump link check for Bio2RDF::Bioportal took 1.9732937812805176s
License | MR license check for Bio2RDF::Bioportal took 0.46148061752319336s
License | HR license check for Bio2RDF::Bioportal took 60.228464126586914s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2587013244628906s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.297107696533203s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.534898042678833s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.23340749740600586s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.24548125267028809s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.23677277565002441s
Performance | Throughput check for Bio2RDF::Bioportal took 11.447889804840088s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 75.50670218467712s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.5457117557525635s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.3462257385253906s
Interlinking | skos check for Bio2RDF::Bioportal took 0.8869349956512451s
Interlinking | skos check for Bio2RDF::Bioportal took 0.3313591480255127s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.24061059951782227s
Currency | Creation date check for Bio2RDF::Bioportal took 0.47194623947143555s
Currency | Modification date check for Bio2RDF::Bioportal took 0.46432948112487793s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 112.81078863143921s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 56.560662269592285s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.419966459274292s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.26398658752441406s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.2575066089630127s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 7.108522176742554s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8897860050201416s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6503603458404541s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.4131138324737549s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.21549439430237s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.341404914855957s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.574002027511597s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.309589147567749s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.526015281677246s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7119588851928711s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.6859407424926758s
Security | Sign check for Bio2RDF::Bioportal took 0.25560474395751953s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 18.60250425338745s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.3969271183013916s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.021333694458007812s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004134178161621094s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 1357.478945016861s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-bioportal took 2434.2285010814667s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.13433408737182617s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.2722170352935791s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.02142930030822754s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.435943603515625e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-chembl took 15.248472929000854s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.4479796886444092s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0006723403930664062s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 20.124848127365112s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.1330206394195557s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 43.148463010787964s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 40.94295334815979s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.222715616226196s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.24329805374145508s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.14378929138183594s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.7887940406799316s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.29363369941711426s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 2.035158634185791s
License | MR license check for Bio2RDF::Clinicaltrials took 0.4642903804779053s
License | HR license check for Bio2RDF::Clinicaltrials took 60.231029748916626s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.23891639709472656s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.151927709579468s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5342481136322021s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.23589491844177246s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.24129199981689453s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.23958182334899902s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.479056596755981s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 75.46124219894409s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.5564734935760498s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.3253774642944336s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.7612173557281494s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.4985935688018799s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.23581576347351074s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.46492981910705566s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.4565091133117676s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 107.7336175441742s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 10.691197872161865s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.389725923538208s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.2514653205871582s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.25029826164245605s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 6.512357234954834s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8803572654724121s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.64353346824646s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.3659379482269287s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 64.68388342857361s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.338467597961426s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 5.7729268074035645s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.27479887008667s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.487250566482544s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.684180736541748s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.39194345474243164s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.24382781982421875s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 10.032614707946777s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.5257112979888916s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.054473876953125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 885.4312093257904s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1896.2667760849s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.4420788288116455s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0005977153778076172s
Extra | Recovery of all triples for Bio2RDF::Ctd took 19.87241506576538s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.1330111026763916s
Amount of data | Number of triples check for Bio2RDF::Ctd took 44.13972568511963s
Interoperability | New terms check for Bio2RDF::Ctd took 42.11280965805054s
Versatility | Languages check for Bio2RDF::Ctd took 60.22564125061035s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.24348998069763184s
Security | Check HTTPS for Bio2RDF::Ctd took 0.14365410804748535s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.3255152702331543s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.28545689582824707s
Availability | RDF dump link check for Bio2RDF::Ctd took 2.1612939834594727s
License | MR license check for Bio2RDF::Ctd took 0.4729771614074707s
License | HR license check for Bio2RDF::Ctd took 60.22912406921387s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.23449039459228516s
Understandability | Number of label check for Bio2RDF::Ctd took 9.352832078933716s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5344514846801758s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.23491740226745605s
Verifiability | Authors check for Bio2RDF::Ctd took 0.23383784294128418s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.23366737365722656s
Performance | Throughput check for Bio2RDF::Ctd took 11.467913627624512s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 73.39674472808838s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.6642210483551025s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.34270715713500977s
Interlinking | skos check for Bio2RDF::Ctd took 0.7726209163665771s
Interlinking | skos check for Bio2RDF::Ctd took 0.35970592498779297s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.23407387733459473s
Currency | Creation date check for Bio2RDF::Ctd took 0.4644911289215088s
Currency | Modification date check for Bio2RDF::Ctd took 0.4639303684234619s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 108.55122184753418s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 928.7974858283997s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.6931421756744385s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.2563812732696533s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.2569766044616699s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 7.256061792373657s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8829452991485596s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6594574451446533s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.394517183303833s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.14258933067322s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.307298183441162s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.2725465297698975s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.2700235843658447s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.496330976486206s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.6794407367706299s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.39307308197021484s
Security | Sign check for Bio2RDF::Ctd took 0.24829530715942383s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 10.812016487121582s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.44392991065979004s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020730257034301758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 7.128715515136719e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 913.8164465427399s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-ctd took 2929.5399215221405s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.26125645637512207s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.023137807846069336s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0009217262268066406s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.507469177246094e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-dataset took 2.7977750301361084s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.44098973274230957s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0007309913635253906s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 19.043871641159058s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.135835886001587s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 44.86981964111328s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.226489782333374s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 13.565752506256104s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.5076184272766113s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.331662654876709s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.29590582847595215s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 26.063955783843994s
License | MR license check for Bio2RDF::Dbsnp took 43.14057946205139s
License | HR license check for Bio2RDF::Dbsnp took 60.525726318359375s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 21.15024733543396s
Understandability | Number of label check for Bio2RDF::Dbsnp took 13.08022165298462s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.8803989887237549s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.23610353469848633s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.23752713203430176s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.23250579833984375s
Performance | Throughput check for Bio2RDF::Dbsnp took 11.455029726028442s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 74.7293541431427s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.23511576652526855s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.33485960960388184s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.7758677005767822s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.3261265754699707s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.2397756576538086s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.47414422035217285s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.4631993770599365s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 106.88350081443787s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 1308.4543626308441s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.7871100902557373s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.26122212409973145s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.2573373317718506s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 7.256211757659912s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8809881210327148s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6562955379486084s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.4022383689880371s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 64.60259652137756s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.3665053844451904s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.290308475494385s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.3017237186431885s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.520007610321045s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.6990246772766113s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.3914909362792969s
Security | Sign check for Bio2RDF::Dbsnp took 0.24381780624389648s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 10.715166807174683s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.46436357498168945s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020739078521728516s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.200241088867188e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 58.37071990966797s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 2459.7293915748596s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.5989573001861572s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0006062984466552734s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 20.281506538391113s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.1805529594421387s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 43.9228937625885s
Interoperability | New terms check for Bio2RDF::Drugbank took 40.71418380737305s
Versatility | Languages check for Bio2RDF::Drugbank took 60.22677946090698s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.24297022819519043s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.14415478706359863s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.5517301559448242s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.2903916835784912s
Availability | RDF dump link check for Bio2RDF::Drugbank took 2.059241533279419s
License | MR license check for Bio2RDF::Drugbank took 0.4430117607116699s
License | HR license check for Bio2RDF::Drugbank took 60.231945514678955s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.23188495635986328s
Understandability | Number of label check for Bio2RDF::Drugbank took 9.754397630691528s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5326244831085205s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.2375497817993164s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.2352750301361084s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.23151087760925293s
Performance | Throughput check for Bio2RDF::Drugbank took 11.467023372650146s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 73.8991379737854s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.5340487957000732s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.354097843170166s
Interlinking | skos check for Bio2RDF::Drugbank took 0.8078386783599854s
Interlinking | skos check for Bio2RDF::Drugbank took 0.35392165184020996s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.24878406524658203s
Currency | Creation date check for Bio2RDF::Drugbank took 0.46474266052246094s
Currency | Modification date check for Bio2RDF::Drugbank took 0.4680976867675781s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 110.96925759315491s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 1321.2780141830444s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.7810840606689453s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.25047731399536133s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.2505531311035156s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 6.9913225173950195s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8805885314941406s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6553423404693604s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.3841526508331299s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 64.87147331237793s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.317707061767578s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.283355474472046s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.2739088535308838s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.490309953689575s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.6814472675323486s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.41512346267700195s
Security | Sign check for Bio2RDF::Drugbank took 0.25067663192749023s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 10.858783960342407s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.6451079845428467s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020704030990600586s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00010657310485839844s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 469.1565582752228s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 2.1219253540039062e-05s
INFO | --- Analysis for bio2rdf-drugbank took 2814.2808208465576s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.4409050941467285s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006175041198730469s
Extra | Recovery of all triples for Bio2RDF::Genage took 17.863478183746338s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.1305418014526367s
Amount of data | Number of triples check for Bio2RDF::Genage took 43.28071045875549s
Interoperability | New terms check for Bio2RDF::Genage took 43.76275587081909s
Versatility | Languages check for Bio2RDF::Genage took 60.22635316848755s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 22.786956548690796s
Security | Check HTTPS for Bio2RDF::Genage took 0.492678165435791s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.4675149917602539s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.2878544330596924s
Availability | RDF dump link check for Bio2RDF::Genage took 6.938382148742676s
License | MR license check for Bio2RDF::Genage took 0.460235595703125s
License | HR license check for Bio2RDF::Genage took 60.226402759552s
Amount of data | Number of property check for Bio2RDF::Genage took 21.068254232406616s
Understandability | Number of label check for Bio2RDF::Genage took 23.153992891311646s
Understandability | URI regex check for Bio2RDF::Genage took 75.09259986877441s
Understandability | Vocabs check for Bio2RDF::Genage took 30.115650177001953s
Verifiability | Authors check for Bio2RDF::Genage took 0.43931031227111816s
Verifiability | Publishers check for Bio2RDF::Genage took 0.23279643058776855s
Performance | Throughput check for Bio2RDF::Genage took 21.287047624588013s
Amount of data | Check the number of entities for Bio2RDF::Genage took 74.48473119735718s
Verifiability | Contribs. check for Bio2RDF::Genage took 11.882036924362183s
Interlinking | sameAs chians check for Bio2RDF::Genage took 30.31824827194214s
Interlinking | skos check for Bio2RDF::Genage took 27.99544095993042s
Interlinking | skos check for Bio2RDF::Genage took 24.063008785247803s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 24.084343194961548s
Currency | Creation date check for Bio2RDF::Genage took 44.69047951698303s
Currency | Modification date check for Bio2RDF::Genage took 58.466787815093994s
Rep.Conc. | URIs length for Bio2RDF::Genage took 121.7792489528656s
Interoperability | New vocabularies check for Bio2RDF::Genage took 1724.1179928779602s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 1.7103092670440674s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.2517964839935303s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.25386571884155273s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.647911548614502s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8816690444946289s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6593818664550781s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.4242551326751709s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.42348146438599s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.3636083602905273s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.150486946105957s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.3118886947631836s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.531206369400024s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7164366245269775s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.3938000202178955s
Security | Sign check for Bio2RDF::Genage took 0.24647927284240723s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 10.649391651153564s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.6331615447998047s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020593643188476562s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.4836273193359375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 64.4217369556427s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-genage took 3240.315598487854s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.43929433822631836s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006377696990966797s
Extra | Recovery of all triples for Bio2RDF::Gendr took 18.707528591156006s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.1366233825683594s
Amount of data | Number of triples check for Bio2RDF::Gendr took 43.82353234291077s
Interoperability | New terms check for Bio2RDF::Gendr took 42.24921178817749s
Versatility | Languages check for Bio2RDF::Gendr took 60.2514545917511s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 4.482331991195679s
Security | Check HTTPS for Bio2RDF::Gendr took 0.14960384368896484s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.24401473999023438s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.2872476577758789s
Availability | RDF dump link check for Bio2RDF::Gendr took 1.9145081043243408s
License | MR license check for Bio2RDF::Gendr took 0.43050312995910645s
License | HR license check for Bio2RDF::Gendr took 60.227959394454956s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.23944807052612305s
Understandability | Number of label check for Bio2RDF::Gendr took 10.52852177619934s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5344328880310059s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.23646759986877441s
Verifiability | Authors check for Bio2RDF::Gendr took 0.23653602600097656s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.23180484771728516s
Performance | Throughput check for Bio2RDF::Gendr took 11.440649032592773s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 75.02646255493164s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.5359811782836914s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.3396022319793701s
Interlinking | skos check for Bio2RDF::Gendr took 0.8942947387695312s
Interlinking | skos check for Bio2RDF::Gendr took 0.40991926193237305s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.23395299911499023s
Currency | Creation date check for Bio2RDF::Gendr took 0.4911668300628662s
Currency | Modification date check for Bio2RDF::Gendr took 0.4681377410888672s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 108.59787273406982s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 110.45725512504578s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.385453462600708s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.25403571128845215s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.25360536575317383s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.414901971817017s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8852086067199707s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6530487537384033s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.38901519775390625s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 64.93786144256592s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.321455478668213s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.371180534362793s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.2776241302490234s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.66940999031067s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.6931345462799072s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.3913700580596924s
Security | Sign check for Bio2RDF::Gendr took 0.2455742359161377s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 18.031164169311523s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.38764381408691406s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 1297.7028958797455s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-gendr took 2430.194820165634s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.43857431411743164s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0003833770751953125s
Extra | Recovery of all triples for Bio2RDF::Goa took 20.40430212020874s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.1387741565704346s
Amount of data | Number of triples check for Bio2RDF::Goa took 44.485929012298584s
Interoperability | New terms check for Bio2RDF::Goa took 43.5532386302948s
Versatility | Languages check for Bio2RDF::Goa took 60.22578477859497s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.24894309043884277s
Security | Check HTTPS for Bio2RDF::Goa took 0.14507436752319336s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.41816186904907227s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.2935667037963867s
Availability | RDF dump link check for Bio2RDF::Goa took 1.8848967552185059s
License | MR license check for Bio2RDF::Goa took 0.45117950439453125s
License | HR license check for Bio2RDF::Goa took 60.229089975357056s
Amount of data | Number of property check for Bio2RDF::Goa took 0.24249482154846191s
Understandability | Number of label check for Bio2RDF::Goa took 10.613666296005249s
Understandability | URI regex check for Bio2RDF::Goa took 0.5371079444885254s
Understandability | Vocabs check for Bio2RDF::Goa took 0.23592329025268555s
Verifiability | Authors check for Bio2RDF::Goa took 0.24695205688476562s
Verifiability | Publishers check for Bio2RDF::Goa took 0.232957124710083s
Performance | Throughput check for Bio2RDF::Goa took 11.447325229644775s
Amount of data | Check the number of entities for Bio2RDF::Goa took 75.31782364845276s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.5351991653442383s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.35092854499816895s
Interlinking | skos check for Bio2RDF::Goa took 1.0757853984832764s
Interlinking | skos check for Bio2RDF::Goa took 0.36115121841430664s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.23720669746398926s
Currency | Creation date check for Bio2RDF::Goa took 0.4651000499725342s
Currency | Modification date check for Bio2RDF::Goa took 0.46828770637512207s
Rep.Conc. | URIs length for Bio2RDF::Goa took 107.50835967063904s
Interoperability | New vocabularies check for Bio2RDF::Goa took 130.22255444526672s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.390977144241333s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.25496745109558105s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.2525458335876465s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.449560165405273s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8789570331573486s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6670730113983154s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.4310886859893799s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.05401492118835s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.520113945007324s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.555006980895996s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3147308826446533s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.56154417991638s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7166900634765625s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.3959524631500244s
Security | Sign check for Bio2RDF::Goa took 0.2471630573272705s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 10.989600419998169s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.5155377388000488s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.0206143856048584s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 464.98177671432495s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-goa took 1603.8140749931335s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.44056057929992676s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0005388259887695312s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 18.29767870903015s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.1825127601623535s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 44.16696262359619s
Interoperability | New terms check for Bio2RDF::Hgnc took 42.42484450340271s
Versatility | Languages check for Bio2RDF::Hgnc took 60.226232290267944s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2690315246582031s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.14274024963378906s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.42484331130981445s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.2936973571777344s
Availability | RDF dump link check for Bio2RDF::Hgnc took 2.0414323806762695s
License | MR license check for Bio2RDF::Hgnc took 0.4519505500793457s
License | HR license check for Bio2RDF::Hgnc took 60.227644205093384s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.23913955688476562s
Understandability | Number of label check for Bio2RDF::Hgnc took 10.391427040100098s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.536475419998169s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.2373816967010498s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.23596668243408203s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.2361307144165039s
Performance | Throughput check for Bio2RDF::Hgnc took 11.51597285270691s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 73.30209755897522s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.542325496673584s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.32356715202331543s
Interlinking | skos check for Bio2RDF::Hgnc took 0.82448410987854s
Interlinking | skos check for Bio2RDF::Hgnc took 0.3449428081512451s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.23632001876831055s
Currency | Creation date check for Bio2RDF::Hgnc took 0.46297621726989746s
Currency | Modification date check for Bio2RDF::Hgnc took 0.4672706127166748s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 107.20488262176514s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 475.0706284046173s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.7202694416046143s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.2560279369354248s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.25493478775024414s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.518563508987427s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8816640377044678s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6501321792602539s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.39305591583251953s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.36761713027954s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 17.602919578552246s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 8.062211036682129s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.2769756317138672s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.494464635849s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7063643932342529s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.3929717540740967s
Security | Sign check for Bio2RDF::Hgnc took 0.23974227905273438s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 12.605798721313477s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.3428664207458496s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.021102428436279297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00010919570922851562s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 477.7134141921997s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1964.8707015514374s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.44313526153564453s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0006034374237060547s
Extra | Recovery of all triples for Bio2RDF::Homologene took 17.737361669540405s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.1303074359893799s
Amount of data | Number of triples check for Bio2RDF::Homologene took 43.924407720565796s
Interoperability | New terms check for Bio2RDF::Homologene took 40.546974658966064s
Versatility | Languages check for Bio2RDF::Homologene took 60.22714948654175s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.2474961280822754s
Security | Check HTTPS for Bio2RDF::Homologene took 0.1423015594482422s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.5787038803100586s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.28712987899780273s
Availability | RDF dump link check for Bio2RDF::Homologene took 1.9739859104156494s
License | MR license check for Bio2RDF::Homologene took 0.46057724952697754s
License | HR license check for Bio2RDF::Homologene took 60.23032331466675s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.23610711097717285s
Understandability | Number of label check for Bio2RDF::Homologene took 9.651337385177612s
Understandability | URI regex check for Bio2RDF::Homologene took 0.5355539321899414s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.2381751537322998s
Verifiability | Authors check for Bio2RDF::Homologene took 0.23649835586547852s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.23387908935546875s
Performance | Throughput check for Bio2RDF::Homologene took 11.429068326950073s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 73.93576407432556s
Verifiability | Contribs. check for Bio2RDF::Homologene took 1.3625824451446533s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.32732653617858887s
Interlinking | skos check for Bio2RDF::Homologene took 0.7049963474273682s
Interlinking | skos check for Bio2RDF::Homologene took 0.32448887825012207s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.23549699783325195s
Currency | Creation date check for Bio2RDF::Homologene took 0.4708554744720459s
Currency | Modification date check for Bio2RDF::Homologene took 0.46236491203308105s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 106.71852445602417s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.8324177265167236s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.2564105987548828s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.25229907035827637s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 6.602807283401489s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.879467248916626s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6495440006256104s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.3918905258178711s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.37259531021118s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.3503997325897217s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.056304693222046s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.2777905464172363s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.50237035751343s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7169167995452881s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.3969407081604004s
Security | Sign check for Bio2RDF::Homologene took 0.2488102912902832s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 13.452706575393677s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.6082584857940674s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020671844482421875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.173683166503906e-05s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-homologene took 2349.7618975639343s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.5937082767486572s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0006394386291503906s
Extra | Recovery of all triples for Bio2RDF::Interpro took 17.928062200546265s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.136141061782837s
Amount of data | Number of triples check for Bio2RDF::Interpro took 43.18810057640076s
Interoperability | New terms check for Bio2RDF::Interpro took 40.215293169021606s
Versatility | Languages check for Bio2RDF::Interpro took 60.22503995895386s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.26404309272766113s
Security | Check HTTPS for Bio2RDF::Interpro took 0.14829254150390625s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.8450815677642822s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.2916111946105957s
Availability | RDF dump link check for Bio2RDF::Interpro took 1.9677989482879639s
License | MR license check for Bio2RDF::Interpro took 0.4560713768005371s
License | HR license check for Bio2RDF::Interpro took 60.23939895629883s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.23850035667419434s
Understandability | Number of label check for Bio2RDF::Interpro took 10.480629920959473s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5325436592102051s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.23456311225891113s
Verifiability | Authors check for Bio2RDF::Interpro took 0.23772907257080078s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.2332017421722412s
Performance | Throughput check for Bio2RDF::Interpro took 11.426433324813843s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 75.89228892326355s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.6672611236572266s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.3374650478363037s
Interlinking | skos check for Bio2RDF::Interpro took 0.7580642700195312s
Interlinking | skos check for Bio2RDF::Interpro took 0.3914821147918701s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2348341941833496s
Currency | Creation date check for Bio2RDF::Interpro took 0.4659411907196045s
Currency | Modification date check for Bio2RDF::Interpro took 0.46726250648498535s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 106.99834322929382s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.4198181629180908s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.2705569267272949s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2524595260620117s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 6.430178642272949s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.88926100730896s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6682953834533691s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.36956286430358887s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.10214018821716s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.3527426719665527s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.5253746509552s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.3221299648284912s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.53842377662659s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7203941345214844s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.4180026054382324s
Security | Sign check for Bio2RDF::Interpro took 0.24634885787963867s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 12.185428857803345s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.33853840827941895s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.021056413650512695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010204315185546875s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-interpro took 1002.3128867149353s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.12931132316589355s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.26193809509277344s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.0210874080657959s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.748603820800781e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-iproclass took 15.380793333053589s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.43984436988830566s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0006992816925048828s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 17.851076364517212s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.1362698078155518s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 43.36773729324341s
Interoperability | New terms check for Bio2RDF::Irefindex took 40.74397134780884s
Versatility | Languages check for Bio2RDF::Irefindex took 60.228668212890625s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.2668576240539551s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.14341998100280762s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.2411212921142578s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.287733793258667s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.0254132747650146s
License | MR license check for Bio2RDF::Irefindex took 0.4143702983856201s
License | HR license check for Bio2RDF::Irefindex took 60.229130029678345s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.23738884925842285s
Understandability | Number of label check for Bio2RDF::Irefindex took 10.204679250717163s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.5348472595214844s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.2408456802368164s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.23900532722473145s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.23290777206420898s
Performance | Throughput check for Bio2RDF::Irefindex took 11.460512161254883s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 77.0978491306305s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.5326735973358154s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.3394277095794678s
Interlinking | skos check for Bio2RDF::Irefindex took 0.7793707847595215s
Interlinking | skos check for Bio2RDF::Irefindex took 0.3818545341491699s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.233994722366333s
Currency | Creation date check for Bio2RDF::Irefindex took 0.46230387687683105s
Currency | Modification date check for Bio2RDF::Irefindex took 0.4665839672088623s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 106.82950854301453s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 910.3558678627014s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.7088437080383301s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.24970483779907227s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.25326037406921387s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 6.502995252609253s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8957204818725586s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6603479385375977s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.3751969337463379s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.2575159072876s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.350252866744995s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 5.638376235961914s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.2750310897827148s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.484068632125854s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.6915040016174316s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.39044857025146484s
Security | Sign check for Bio2RDF::Irefindex took 0.24563956260681152s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 12.929015874862671s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.4385373592376709s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.02141284942626953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.487701416015625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 98.82150673866272s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-irefindex took 2000.5370197296143s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.1296088695526123s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2754795551300049s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020298242568969727s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0006759166717529297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 2.8133392333984375e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-linkedspl took 8.5551016330719s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.440091609954834s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0005829334259033203s
Extra | Recovery of all triples for Bio2RDF::Lsr took 18.96855401992798s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.137732744216919s
Amount of data | Number of triples check for Bio2RDF::Lsr took 43.38929104804993s
Interoperability | New terms check for Bio2RDF::Lsr took 41.49827861785889s
Versatility | Languages check for Bio2RDF::Lsr took 60.225265979766846s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.2509145736694336s
Security | Check HTTPS for Bio2RDF::Lsr took 0.14172148704528809s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.6596014499664307s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.2804598808288574s
Availability | RDF dump link check for Bio2RDF::Lsr took 1.849930763244629s
License | MR license check for Bio2RDF::Lsr took 0.4381580352783203s
License | HR license check for Bio2RDF::Lsr took 60.24732279777527s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.2398850917816162s
Understandability | Number of label check for Bio2RDF::Lsr took 9.501236915588379s
Understandability | URI regex check for Bio2RDF::Lsr took 0.5416240692138672s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.23787331581115723s
Verifiability | Authors check for Bio2RDF::Lsr took 0.23916101455688477s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.23453354835510254s
Performance | Throughput check for Bio2RDF::Lsr took 11.47376012802124s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 76.25260186195374s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.7065775394439697s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3323667049407959s
Interlinking | skos check for Bio2RDF::Lsr took 0.6710085868835449s
Interlinking | skos check for Bio2RDF::Lsr took 0.32775139808654785s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.23579835891723633s
Currency | Creation date check for Bio2RDF::Lsr took 0.48384547233581543s
Currency | Modification date check for Bio2RDF::Lsr took 0.46901988983154297s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 108.34394001960754s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 73.56467843055725s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.3910856246948242s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.25186920166015625s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.25414133071899414s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 6.9475579261779785s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8928015232086182s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6467509269714355s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.406552791595459s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 64.83963131904602s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.332420825958252s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.470034837722778s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.2645745277404785s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.480016231536865s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.6870791912078857s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.5693159103393555s
Security | Sign check for Bio2RDF::Lsr took 0.26290035247802734s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 13.083254098892212s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.49614572525024414s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.021780014038085938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0009515285491943359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 6.0558319091796875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 74.32885432243347s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.7404556274414062e-05s
INFO | --- Analysis for bio2rdf-lsr took 1145.6359610557556s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.440631628036499s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0006158351898193359s
Extra | Recovery of all triples for Bio2RDF::Mesh took 17.466574907302856s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.141021966934204s
Amount of data | Number of triples check for Bio2RDF::Mesh took 43.57484436035156s
Interoperability | New terms check for Bio2RDF::Mesh took 39.86067032814026s
Versatility | Languages check for Bio2RDF::Mesh took 60.224766969680786s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.24213695526123047s
Security | Check HTTPS for Bio2RDF::Mesh took 0.14217233657836914s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.47759151458740234s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.28549623489379883s
Availability | RDF dump link check for Bio2RDF::Mesh took 1.9807686805725098s
License | MR license check for Bio2RDF::Mesh took 0.3345003128051758s
License | HR license check for Bio2RDF::Mesh took 60.228325843811035s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.2390897274017334s
Understandability | Number of label check for Bio2RDF::Mesh took 9.292577505111694s
Understandability | URI regex check for Bio2RDF::Mesh took 0.558781623840332s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.23542094230651855s
Verifiability | Authors check for Bio2RDF::Mesh took 0.24119925498962402s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.23271799087524414s
Performance | Throughput check for Bio2RDF::Mesh took 11.345561742782593s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 73.94147968292236s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.5491302013397217s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.3183481693267822s
Interlinking | skos check for Bio2RDF::Mesh took 0.6826503276824951s
Interlinking | skos check for Bio2RDF::Mesh took 0.3240532875061035s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.23455452919006348s
Currency | Creation date check for Bio2RDF::Mesh took 0.4694671630859375s
Currency | Modification date check for Bio2RDF::Mesh took 0.470111608505249s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 108.15252542495728s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 1337.5238189697266s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.8049294948577881s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2518327236175537s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.25270700454711914s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 7.820814609527588s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.884906530380249s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6510660648345947s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.37288641929626465s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 64.89278793334961s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.3335225582122803s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.39950156211853s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.311816692352295s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.54037356376648s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.6920878887176514s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.3966503143310547s
Security | Sign check for Bio2RDF::Mesh took 0.2503175735473633s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 10.572569608688354s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.44661521911621094s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.796287536621094e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 916.2795498371124s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-mesh took 3246.782424211502s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.43900537490844727s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0005891323089599609s
Extra | Recovery of all triples for Bio2RDF::Mgi took 17.828083992004395s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.1410608291625977s
Amount of data | Number of triples check for Bio2RDF::Mgi took 43.128695011138916s
Interoperability | New terms check for Bio2RDF::Mgi took 40.48313784599304s
Versatility | Languages check for Bio2RDF::Mgi took 60.22073721885681s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.24783039093017578s
Security | Check HTTPS for Bio2RDF::Mgi took 0.14220428466796875s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.7132318019866943s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.2878403663635254s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.087939739227295s
License | MR license check for Bio2RDF::Mgi took 0.4349985122680664s
License | HR license check for Bio2RDF::Mgi took 60.22839045524597s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.23418688774108887s
Understandability | Number of label check for Bio2RDF::Mgi took 10.396060943603516s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5341291427612305s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.23568201065063477s
Verifiability | Authors check for Bio2RDF::Mgi took 0.23343467712402344s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.23362469673156738s
Performance | Throughput check for Bio2RDF::Mgi took 11.549602031707764s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 72.97848320007324s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.7019557952880859s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.3192737102508545s
Interlinking | skos check for Bio2RDF::Mgi took 0.9110007286071777s
Interlinking | skos check for Bio2RDF::Mgi took 0.322176456451416s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.23672151565551758s
Currency | Creation date check for Bio2RDF::Mgi took 0.46643590927124023s
Currency | Modification date check for Bio2RDF::Mgi took 0.46668171882629395s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 107.99608612060547s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 890.654256105423s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.7298493385314941s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.24950051307678223s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.2491142749786377s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.138239860534668s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.892848014831543s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.659221887588501s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.35506105422973633s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.04564809799194s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.3360893726348877s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.022950172424316s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.272585391998291s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.494569540023804s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7011804580688477s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.39404869079589844s
Security | Sign check for Bio2RDF::Mgi took 0.24264979362487793s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 11.956893920898438s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.6158478260040283s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 8.797645568847656e-05s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-mgi took 2784.205130815506s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.43983960151672363s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0005829334259033203s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 19.961050748825073s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.1399586200714111s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 44.16962122917175s
Interoperability | New terms check for Bio2RDF::Ncbigene took 54.75034022331238s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.22527503967285s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.24563026428222656s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.14486956596374512s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.5328547954559326s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.28570127487182617s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 2.00907826423645s
License | MR license check for Bio2RDF::Ncbigene took 0.44750261306762695s
License | HR license check for Bio2RDF::Ncbigene took 60.230698108673096s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.24233794212341309s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.752456188201904s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.5343973636627197s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.23681640625s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.235870361328125s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.23487591743469238s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.494313955307007s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 72.48059463500977s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.5601935386657715s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.3296685218811035s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.7554733753204346s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.3213984966278076s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.23520350456237793s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.4674351215362549s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.4692373275756836s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 108.43568181991577s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 49.59989380836487s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.39424943923950195s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2582693099975586s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.24898290634155273s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.265801191329956s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8830018043518066s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6372191905975342s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.40100622177124023s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 64.87939953804016s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.31443190574646s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.260839939117432s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.2750587463378906s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.48927450180054s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.6917517185211182s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.5708644390106201s
Security | Sign check for Bio2RDF::Ncbigene took 0.24421167373657227s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 17.520270109176636s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.3983020782470703s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012135505676269531s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 63.278225898742676s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1132.4083797931671s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.44087886810302734s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0006582736968994141s
Extra | Recovery of all triples for Bio2RDF::Ndc took 18.0497624874115s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.1426546573638916s
Amount of data | Number of triples check for Bio2RDF::Ndc took 43.34299445152283s
Interoperability | New terms check for Bio2RDF::Ndc took 40.538665771484375s
Versatility | Languages check for Bio2RDF::Ndc took 60.22333741188049s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.2468860149383545s
Security | Check HTTPS for Bio2RDF::Ndc took 0.14339709281921387s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.8692281246185303s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.28973865509033203s
Availability | RDF dump link check for Bio2RDF::Ndc took 1.9355151653289795s
License | MR license check for Bio2RDF::Ndc took 0.5763230323791504s
License | HR license check for Bio2RDF::Ndc took 60.23300552368164s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.2349255084991455s
Understandability | Number of label check for Bio2RDF::Ndc took 9.333902597427368s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5579030513763428s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.24197864532470703s
Verifiability | Authors check for Bio2RDF::Ndc took 0.23537588119506836s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.24774909019470215s
Performance | Throughput check for Bio2RDF::Ndc took 11.499166011810303s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 75.96220302581787s
Verifiability | Contribs. check for Bio2RDF::Ndc took 1.4305405616760254s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.34058427810668945s
Interlinking | skos check for Bio2RDF::Ndc took 0.7856817245483398s
Interlinking | skos check for Bio2RDF::Ndc took 0.3263239860534668s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.23615264892578125s
Currency | Creation date check for Bio2RDF::Ndc took 0.46335864067077637s
Currency | Modification date check for Bio2RDF::Ndc took 0.4645678997039795s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 108.60859870910645s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 77.37001585960388s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.41674160957336426s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2507953643798828s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.25897693634033203s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 7.447129964828491s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.885552167892456s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6477432250976562s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.431293249130249s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.47473883628845s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.3584070205688477s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 5.9187610149383545s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.27634596824646s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.48954200744629s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7031853199005127s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.5466973781585693s
Security | Sign check for Bio2RDF::Ndc took 0.2455737590789795s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 9.5916907787323s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.340970516204834s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020888805389404297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 65.10457515716553s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-ndc took 1134.1855175495148s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.1262814998626709s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.26719188690185547s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.02104926109313965s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.457069396972656e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-nextprot took 3.408271551132202s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.4416635036468506s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0006814002990722656s
Extra | Recovery of all triples for Bio2RDF::Omim took 18.688106775283813s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.1412603855133057s
Amount of data | Number of triples check for Bio2RDF::Omim took 44.710262298583984s
Interoperability | New terms check for Bio2RDF::Omim took 41.56986856460571s
Versatility | Languages check for Bio2RDF::Omim took 60.24828743934631s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.24967265129089355s
Security | Check HTTPS for Bio2RDF::Omim took 0.14451241493225098s
Interpretability | RDF structures check for Bio2RDF::Omim took 1.1846840381622314s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.29659223556518555s
Availability | RDF dump link check for Bio2RDF::Omim took 1.9394843578338623s
License | MR license check for Bio2RDF::Omim took 0.4670114517211914s
License | HR license check for Bio2RDF::Omim took 60.22869372367859s
Amount of data | Number of property check for Bio2RDF::Omim took 0.23462438583374023s
Understandability | Number of label check for Bio2RDF::Omim took 9.856752157211304s
Understandability | URI regex check for Bio2RDF::Omim took 0.5375275611877441s
Understandability | Vocabs check for Bio2RDF::Omim took 0.23556160926818848s
Verifiability | Authors check for Bio2RDF::Omim took 0.23759698867797852s
Verifiability | Publishers check for Bio2RDF::Omim took 0.23473048210144043s
Performance | Throughput check for Bio2RDF::Omim took 11.533166408538818s
Amount of data | Check the number of entities for Bio2RDF::Omim took 72.7160336971283s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.5353686809539795s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.3552887439727783s
Interlinking | skos check for Bio2RDF::Omim took 1.0348806381225586s
Interlinking | skos check for Bio2RDF::Omim took 0.359663724899292s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.23397517204284668s
Currency | Creation date check for Bio2RDF::Omim took 0.46234774589538574s
Currency | Modification date check for Bio2RDF::Omim took 0.46427369117736816s
Rep.Conc. | URIs length for Bio2RDF::Omim took 110.17165684700012s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.39745140075683594s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.2538425922393799s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.25222206115722656s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 6.610504150390625s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8936951160430908s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6423680782318115s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.37894654273986816s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 64.81436610221863s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.3519229888916016s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 5.877167224884033s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.274491786956787s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.5239794254303s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7053759098052979s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.39011049270629883s
Security | Sign check for Bio2RDF::Omim took 0.24705243110656738s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 10.625756025314331s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.6043002605438232s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.021038055419921875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00013327598571777344s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-omim took 1002.9959890842438s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 8.845329284667969e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.2894628047943115s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.022944211959838867s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.1484832763671875e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 2.7096846103668213s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.44144535064697266s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0005779266357421875s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 18.50522232055664s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.1491541862487793s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 43.6814820766449s
Interoperability | New terms check for Bio2RDF::Orphanet took 40.864391803741455s
Versatility | Languages check for Bio2RDF::Orphanet took 60.25129747390747s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.2480151653289795s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.14372968673706055s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.7490477561950684s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.2861666679382324s
Availability | RDF dump link check for Bio2RDF::Orphanet took 1.8941090106964111s
License | MR license check for Bio2RDF::Orphanet took 0.4920814037322998s
License | HR license check for Bio2RDF::Orphanet took 60.22621941566467s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.23291778564453125s
Understandability | Number of label check for Bio2RDF::Orphanet took 9.872007369995117s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5352039337158203s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.2302227020263672s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.23410630226135254s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.23095154762268066s
Performance | Throughput check for Bio2RDF::Orphanet took 11.54092288017273s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 76.9630959033966s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.5329253673553467s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.322476863861084s
Interlinking | skos check for Bio2RDF::Orphanet took 0.7391018867492676s
Interlinking | skos check for Bio2RDF::Orphanet took 0.4261000156402588s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.2331693172454834s
Currency | Creation date check for Bio2RDF::Orphanet took 0.46316003799438477s
Currency | Modification date check for Bio2RDF::Orphanet took 0.4559307098388672s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 106.98034715652466s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 53.682169675827026s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.3937644958496094s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2546370029449463s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.25855469703674316s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 6.776442766189575s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8797895908355713s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6591372489929199s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.47626519203186035s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 64.85517239570618s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.3868086338043213s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.390904664993286s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.303804874420166s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.51650094985962s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7047216892242432s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.5440809726715088s
Security | Sign check for Bio2RDF::Orphanet took 0.24639606475830078s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 9.592068195343018s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.340970516204834s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02110576629638672s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.416175842285156e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 77.92266941070557s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1125.7276797294617s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.13083958625793457s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.2677285671234131s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.218650817871094e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-pathwaycommons took 8.385369777679443s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.445758581161499s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0006051063537597656s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 18.275015830993652s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.1366517543792725s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 43.60919117927551s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 40.70638108253479s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.22653913497925s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.24801349639892578s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.1431407928466797s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.7523248195648193s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.2863917350769043s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 2.0015320777893066s
License | MR license check for Bio2RDF::Pharmgkb took 0.44829726219177246s
License | HR license check for Bio2RDF::Pharmgkb took 60.227487564086914s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.23192548751831055s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 9.529906511306763s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5377545356750488s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.23316359519958496s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.23434782028198242s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.2431788444519043s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.478625059127808s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 76.92411780357361s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.5587432384490967s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.32706546783447266s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.9705843925476074s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.32762813568115234s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.2342994213104248s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.4642186164855957s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.463604211807251s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 108.19641041755676s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 25.733999729156494s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.3891489505767822s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.25815558433532715s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.2560875415802002s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 7.223336696624756s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8826375007629395s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6450972557067871s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.39861226081848145s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 64.88229203224182s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.357501983642578s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.251845121383667s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.2803246974945068s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.49041438102722s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.6893351078033447s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.3941187858581543s
Security | Sign check for Bio2RDF::Pharmgkb took 0.24913740158081055s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 9.96377158164978s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.43175578117370605s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.020974397659301758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0006835460662841797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 9.250640869140625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 984.9131672382355s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 2004.5362849235535s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.4415149688720703s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0005512237548828125s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 17.75180983543396s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.1325366497039795s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 44.99788999557495s
Interoperability | New terms check for Bio2RDF::Pubmed took 40.9278347492218s
Versatility | Languages check for Bio2RDF::Pubmed took 60.23001480102539s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.2530231475830078s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.14587163925170898s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 1.2266085147857666s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.286884069442749s
Availability | RDF dump link check for Bio2RDF::Pubmed took 1.9618735313415527s
License | MR license check for Bio2RDF::Pubmed took 0.5659651756286621s
License | HR license check for Bio2RDF::Pubmed took 60.230926752090454s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.2385883331298828s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.341402530670166s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5409858226776123s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.23548269271850586s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.2406299114227295s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.234208345413208s
Performance | Throughput check for Bio2RDF::Pubmed took 11.420384883880615s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 72.27463436126709s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.5643055438995361s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.3371725082397461s
Interlinking | skos check for Bio2RDF::Pubmed took 0.8273911476135254s
Interlinking | skos check for Bio2RDF::Pubmed took 0.31841516494750977s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.23047256469726562s
Currency | Creation date check for Bio2RDF::Pubmed took 0.46613335609436035s
Currency | Modification date check for Bio2RDF::Pubmed took 0.4800131320953369s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 107.39868831634521s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 23.209291458129883s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.39308857917785645s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.25299715995788574s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.2505977153778076s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 7.50242805480957s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8917818069458008s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6568996906280518s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.4626176357269287s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.53872179985046s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.340824842453003s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.1939311027526855s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.3150243759155273s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.53638005256653s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.6921801567077637s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.3912825584411621s
Security | Sign check for Bio2RDF::Pubmed took 0.24649572372436523s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 10.795542240142822s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.2185807228088379s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020722150802612305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.0001506805419921875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 495.4723172187805s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.5735626220703125e-05s
INFO | --- Analysis for bio2rdf-pubmed took 1506.7957799434662s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.1307382583618164s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0008041858673095703s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.26532459259033203s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.022060394287109375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 0.00010371208190917969s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-sabiork took 8.556302070617676s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.4452998638153076s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0005805492401123047s
Extra | Recovery of all triples for Bio2RDF::Sgd took 18.09654998779297s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.1346828937530518s
Amount of data | Number of triples check for Bio2RDF::Sgd took 45.12628531455994s
Interoperability | New terms check for Bio2RDF::Sgd took 40.514981746673584s
Versatility | Languages check for Bio2RDF::Sgd took 60.226683378219604s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.24795198440551758s
Security | Check HTTPS for Bio2RDF::Sgd took 0.143784761428833s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.49120306968688965s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.28330206871032715s
Availability | RDF dump link check for Bio2RDF::Sgd took 1.8016653060913086s
License | MR license check for Bio2RDF::Sgd took 0.3721792697906494s
License | HR license check for Bio2RDF::Sgd took 60.23011350631714s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.2337355613708496s
Understandability | Number of label check for Bio2RDF::Sgd took 9.880912065505981s
Understandability | URI regex check for Bio2RDF::Sgd took 0.53497314453125s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2399446964263916s
Verifiability | Authors check for Bio2RDF::Sgd took 0.23808002471923828s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.23450255393981934s
Performance | Throughput check for Bio2RDF::Sgd took 11.473573207855225s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 75.71174812316895s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.5684638023376465s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.33692359924316406s
Interlinking | skos check for Bio2RDF::Sgd took 0.7953417301177979s
Interlinking | skos check for Bio2RDF::Sgd took 0.3272106647491455s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2336130142211914s
Currency | Creation date check for Bio2RDF::Sgd took 0.47045040130615234s
Currency | Modification date check for Bio2RDF::Sgd took 0.4696195125579834s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 112.28798270225525s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 500.3114445209503s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 2.1676907539367676s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.24773812294006348s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.25081372261047363s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.19449782371521s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.8955094814300537s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6457178592681885s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.35825490951538086s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 64.58290934562683s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.328403949737549s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.060364007949829s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.302616834640503s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.52882218360901s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.708594799041748s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.3954904079437256s
Security | Sign check for Bio2RDF::Sgd took 0.2470400333404541s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 11.9236319065094s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.34343552589416504s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.02060246467590332s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010395050048828125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 40.71904802322388s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-sgd took 1537.6646184921265s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.315376281738281e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.25588345527648926s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.337860107421875e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 2.722745180130005s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.438784122467041s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0006604194641113281s
Extra | Recovery of all triples for Bio2RDF::Sider took 17.778926849365234s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.1258480548858643s
Amount of data | Number of triples check for Bio2RDF::Sider took 43.66324257850647s
Interoperability | New terms check for Bio2RDF::Sider took 41.859163999557495s
Versatility | Languages check for Bio2RDF::Sider took 60.24960923194885s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.24773168563842773s
Security | Check HTTPS for Bio2RDF::Sider took 0.14316034317016602s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.4412205219268799s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.2871887683868408s
Availability | RDF dump link check for Bio2RDF::Sider took 2.014554023742676s
License | MR license check for Bio2RDF::Sider took 0.4504384994506836s
License | HR license check for Bio2RDF::Sider took 60.23304557800293s
Amount of data | Number of property check for Bio2RDF::Sider took 0.23270559310913086s
Understandability | Number of label check for Bio2RDF::Sider took 10.289845943450928s
Understandability | URI regex check for Bio2RDF::Sider took 0.5358455181121826s
Understandability | Vocabs check for Bio2RDF::Sider took 0.23458170890808105s
Verifiability | Authors check for Bio2RDF::Sider took 0.23825955390930176s
Verifiability | Publishers check for Bio2RDF::Sider took 0.23363542556762695s
Performance | Throughput check for Bio2RDF::Sider took 11.446593046188354s
Amount of data | Check the number of entities for Bio2RDF::Sider took 76.98783922195435s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.534231424331665s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.33336305618286133s
Interlinking | skos check for Bio2RDF::Sider took 0.6591830253601074s
Interlinking | skos check for Bio2RDF::Sider took 0.3303041458129883s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.23546814918518066s
Currency | Creation date check for Bio2RDF::Sider took 0.46068239212036133s
Currency | Modification date check for Bio2RDF::Sider took 0.4644601345062256s
Rep.Conc. | URIs length for Bio2RDF::Sider took 109.70768690109253s
Interoperability | New vocabularies check for Bio2RDF::Sider took 466.87479043006897s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.7288608551025391s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.2517516613006592s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2495114803314209s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 7.057138204574585s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8790097236633301s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6488850116729736s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.36447834968566895s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 64.87189245223999s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.355400800704956s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.523566961288452s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.3093273639678955s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.50214123725891s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.6882469654083252s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.40514707565307617s
Security | Sign check for Bio2RDF::Sider took 0.2480020523071289s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 9.713150024414062s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.3149223327636719s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020721435546875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 3.910064697265625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 10.690062284469604s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-sider took 1478.2783946990967s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 0.00010824203491210938s
Availability | VoID file availability check for bio2rdf-taxon took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.26150035858154297s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.0203399658203125s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.315376281738281e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-taxon took 2.671621799468994s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.5897750854492188s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0005645751953125s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 19.214397430419922s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.1355974674224854s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 44.1603307723999s
Interoperability | New terms check for Bio2RDF::Taxonomy took 42.151153564453125s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.2504997253418s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.24786829948425293s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.1497495174407959s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.3522493839263916s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.2863590717315674s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 1.85526704788208s
License | MR license check for Bio2RDF::Taxonomy took 0.5096676349639893s
License | HR license check for Bio2RDF::Taxonomy took 60.22934293746948s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.23784995079040527s
Understandability | Number of label check for Bio2RDF::Taxonomy took 10.091874122619629s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5358374118804932s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.23654389381408691s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.23510384559631348s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.2416062355041504s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.464271783828735s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 74.99271750450134s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.5335910320281982s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.32715487480163574s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.7492530345916748s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.3444182872772217s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.23341107368469238s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.46233487129211426s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.46707940101623535s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 107.33721780776978s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 863.9114997386932s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.6996827125549316s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.2572503089904785s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.2502474784851074s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 6.921214818954468s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8822226524353027s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6673336029052734s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.3720827102661133s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.42710041999817s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.3800723552703857s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.106765270233154s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.2786881923675537s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.54327154159546s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7032320499420166s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.3939347267150879s
Security | Sign check for Bio2RDF::Taxonomy took 0.24309277534484863s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 9.95230770111084s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.5440170764923096s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.021124601364135742s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010275840759277344s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 905.3513875007629s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 2764.2022507190704s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.13190412521362305s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.00067138671875s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.2704775333404541s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020364999771118164s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 15.299904108047485s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.4408552646636963s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0008263587951660156s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 17.882598400115967s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.1334941387176514s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 43.483513832092285s
Interoperability | New terms check for Bio2RDF::Wormbase took 39.62723517417908s
Versatility | Languages check for Bio2RDF::Wormbase took 60.226824045181274s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.24696111679077148s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.1435832977294922s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.4921605587005615s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.2874627113342285s
Availability | RDF dump link check for Bio2RDF::Wormbase took 2.114635467529297s
License | MR license check for Bio2RDF::Wormbase took 0.46284055709838867s
License | HR license check for Bio2RDF::Wormbase took 60.23020601272583s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.23948907852172852s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.49747109413147s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.5365509986877441s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.23321127891540527s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.24207472801208496s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.23563647270202637s
Performance | Throughput check for Bio2RDF::Wormbase took 11.448619365692139s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 74.91596269607544s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.5630576610565186s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.3424339294433594s
Interlinking | skos check for Bio2RDF::Wormbase took 0.9302880764007568s
Interlinking | skos check for Bio2RDF::Wormbase took 0.32566165924072266s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.23335027694702148s
Currency | Creation date check for Bio2RDF::Wormbase took 0.4676785469055176s
Currency | Modification date check for Bio2RDF::Wormbase took 0.4755825996398926s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 107.43221640586853s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 55.690937757492065s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.39414477348327637s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.25763964653015137s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.2560551166534424s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 6.473329782485962s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8798978328704834s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6547269821166992s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.35732340812683105s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.2605152130127s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.33778977394104s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 5.976991891860962s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.309971809387207s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.53518319129944s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7048416137695312s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.5759665966033936s
Security | Sign check for Bio2RDF::Wormbase took 0.24460554122924805s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 11.003755569458008s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.4380929470062256s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.021257638931274414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.273124694824219e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 1788.9981272220612s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.6689300537109375e-05s
INFO | --- Analysis for bio2rdf-wormbase took 2836.4647812843323s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 9.608268737792969e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.2645227909088135s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.020459413528442383s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.3113021850585938e-05s
Believability | Calculation of trust value for Biografías y Vidas took 1.0967254638671875e-05s
INFO | --- Analysis for biografiasyvidas took 2.4412243366241455s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.5348455905914307s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.264298677444458s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.02288651466369629s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.0108642578125e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 9.775161743164062e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 2.9474985599517822s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 8.630752563476562e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.2714266777038574s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020959854125976562s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 3.743171691894531e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.0728836059570312e-05s
INFO | --- Analysis for biolod-pdb took 7.381595611572266s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.4684722423553467s
Availability | VoID file availability check for BioModels RDF took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.2675297260284424s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020879268646240234s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.695487976074219e-05s
Believability | Calculation of trust value for BioModels RDF took 1.1444091796875e-05s
INFO | --- Analysis for biomodels-rdf took 3.5756850242614746s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.0500521659851074s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.26712489128112793s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020849943161010742s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0251998901367188e-05s
INFO | --- Analysis for Biop took 6.145685434341431s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.000110626220703125s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.27240681648254395s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02113819122314453s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.457069396972656e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.2159347534179688e-05s
INFO | --- Analysis for Bioportal took 2.4901785850524902s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.4345855712890625e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.27074265480041504s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020872116088867188s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006144046783447266s
Believability | Calculation of trust value for Amphibian gross anatomy took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-aao took 4.480903625488281s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 8.7738037109375e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.2632768154144287s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.020512819290161133s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0002923011779785156s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-aba took 3.894552707672119s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2758195400238037s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.02168750762939453s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015363693237304688s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-acgt took 3.89867901802063s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.38690185546875e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0007729530334472656s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.2636141777038574s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.022403955459594727s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003376007080078125s
Believability | Calculation of trust value for Animal natural history and life history took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-adw took 3.9720206260681152s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.2644836902618408s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020360708236694336s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004534721374511719s
Believability | Calculation of trust value for Anatomical Entity Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-aeo took 4.225155353546143s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.2704601287841797s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.020462989807128906s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009284019470214844s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-aero took 4.028164625167847s
Availability | SPARQL endpoint availability check for AI/RHEUM took 8.463859558105469e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.271359920501709s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020847082138061523s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0003960132598876953s
Believability | Calculation of trust value for AI/RHEUM took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-air took 4.237099885940552s
Availability | SPARQL endpoint availability check for Amino Acid took 0.00012540817260742188s
Availability | VoID file availability check for Amino Acid took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.2547605037689209s
Reputation | Calculation of the PageRank for Amino Acid took 0.029422283172607422s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0013756752014160156s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00036263465881347656s
Believability | Calculation of trust value for Amino Acid took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-amino-acid took 4.098505735397339s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 5.91278076171875e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0009086132049560547s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.2537674903869629s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.02134871482849121s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002880096435546875s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-apo took 3.7809693813323975s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.315376281738281e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.25685882568359375s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.0002384185791015625s
Believability | Calculation of trust value for African Traditional Medicine took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-atmo took 4.271063566207886s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.267692565917969e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.2630949020385742s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020780563354492188s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.179115295410156e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ato took 3.7788631916046143s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.2557086944580078s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0012507438659667969s
Believability | Calculation of trust value for BioAssay Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bao took 3.7925655841827393s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.506111145019531e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0003783702850341797s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.26487255096435547s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020328521728515625s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00036787986755371094s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 3.801826238632202s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.00037479400634765625s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.26317739486694336s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003597736358642578s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-bcgo took 3.6911470890045166s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.00041675567626953125s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.25515007972717285s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0013642311096191406s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bdo took 4.008651971817017s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 7.581710815429688e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.00036907196044921875s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.2616603374481201s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.00046896934509277344s
Believability | Calculation of trust value for Basic Formal Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bfo took 3.799276113510132s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 0.00011920928955078125s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.27880048751831055s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.02054619789123535s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0006952285766601562s
Believability | Calculation of trust value for Bleeding History Phenotype took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bho took 4.3220179080963135s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 0.00010347366333007812s
Availability | VoID file availability check for Bilateria anatomy took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.26093292236328125s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004429817199707031s
Believability | Calculation of trust value for Bilateria anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bila took 3.918051242828369s
Availability | SPARQL endpoint availability check for BIRNLex took 4.482269287109375e-05s
Availability | VoID file availability check for BIRNLex took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.2698545455932617s
Reputation | Calculation of the PageRank for BIRNLex took 0.020930051803588867s
Interlinking | Calculation of Degree of Connection for BIRNLex took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014472007751464844s
Believability | Calculation of trust value for BIRNLex took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-birnlex took 4.030142784118652s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 9.107589721679688e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.26406192779541016s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.0208590030670166s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0008063316345214844s
Believability | Calculation of trust value for Gene Regulation Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bootstrep took 3.909963846206665s
Availability | SPARQL endpoint availability check for BioPAX took 9.012222290039062e-05s
Availability | VoID file availability check for BioPAX took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for BioPAX took 0.266873836517334s
Reputation | Calculation of the PageRank for BioPAX took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for BioPAX took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BioPAX took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.608268737792969e-05s
Believability | Calculation of trust value for BioPAX took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-bp took 3.800184488296509s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 9.107589721679688e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.2705702781677246s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.022490978240966797s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003104209899902344s
Believability | Calculation of trust value for Biomedical Resource Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bro_x1 took 4.07320499420166s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.26618528366088867s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.021534204483032227s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0006823539733886719s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.000202178955078125s
Believability | Calculation of trust value for Spatial Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bspo took 3.894211769104004s
Availability | SPARQL endpoint availability check for BioTop took 4.38690185546875e-05s
Availability | VoID file availability check for BioTop took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for BioTop took 0.267103910446167s
Reputation | Calculation of the PageRank for BioTop took 0.02176046371459961s
Interlinking | Calculation of Degree of Connection for BioTop took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006334781646728516s
Believability | Calculation of trust value for BioTop took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bt took 4.058251857757568s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 8.869171142578125e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.2702178955078125s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.022346973419189453s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008394718170166016s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bto took 3.9172184467315674s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3092472553253174s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.021344423294067383s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0017693042755126953s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-canco took 4.2633795738220215s
Availability | SPARQL endpoint availability check for CAO took 8.988380432128906e-05s
Availability | VoID file availability check for CAO took 0.0007448196411132812s
Completeness | Calculation of interlinking completeness for CAO took 0.2703545093536377s
Reputation | Calculation of the PageRank for CAO took 0.020835399627685547s
Interlinking | Calculation of Degree of Connection for CAO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CAO took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0005695819854736328s
Believability | Calculation of trust value for CAO took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cao took 3.841722011566162s
Availability | SPARQL endpoint availability check for CareLex took 8.821487426757812e-05s
Availability | VoID file availability check for CareLex took 0.0007805824279785156s
Completeness | Calculation of interlinking completeness for CareLex took 0.26408839225769043s
Reputation | Calculation of the PageRank for CareLex took 0.020236492156982422s
Interlinking | Calculation of Degree of Connection for CareLex took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CareLex took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.9114227294921875e-05s
Believability | Calculation of trust value for CareLex took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-carelex took 3.785656690597534s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0007784366607666016s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.2731516361236572s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.000774383544921875s
Believability | Calculation of trust value for Cell Cycle Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cco took 3.8117475509643555s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.2671823501586914s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.02108931541442871s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00025272369384765625s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-cdao took 3.9763412475585938s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 9.870529174804688e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2771477699279785s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.02063775062561035s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007481575012207031s
Believability | Calculation of trust value for Chemical entities of biological interest took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-chebi took 3.880605459213257s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.4345855712890625e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.27073168754577637s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.02073955535888672s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002465248107910156s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 3.803062915802002s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.28597307205200195s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020860671997070312s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007233619689941406s
Believability | Calculation of trust value for Chemical Information Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cheminf took 3.812624931335449s
Availability | SPARQL endpoint availability check for Cell type took 8.893013000488281e-05s
Availability | VoID file availability check for Cell type took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for Cell type took 0.27253079414367676s
Reputation | Calculation of the PageRank for Cell type took 0.020891904830932617s
Interlinking | Calculation of Degree of Connection for Cell type took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003705024719238281s
Believability | Calculation of trust value for Cell type took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-cl took 3.8146724700927734s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0008363723754882812s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.26675844192504883s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020845890045166016s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0007855892181396484s
Believability | Calculation of trust value for Cell Line Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-clo took 3.803323745727539s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 5.8650970458984375e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.2670738697052002s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020537853240966797s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00016307830810546875s
Believability | Calculation of trust value for Clinical Measurement Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cmo took 3.745323657989502s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 9.822845458984375e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0007445812225341797s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.2641756534576416s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.021085023880004883s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00019860267639160156s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cno took 3.974550247192383s
Availability | SPARQL endpoint availability check for Wheat trait took 9.107589721679688e-05s
Availability | VoID file availability check for Wheat trait took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.2633626461029053s
Reputation | Calculation of the PageRank for Wheat trait took 0.02281022071838379s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.340576171875e-05s
Believability | Calculation of trust value for Wheat trait took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-co_wheat took 4.101864814758301s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.7206878662109375e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.264117956161499s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.021828889846801758s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003535747528076172s
Believability | Calculation of trust value for Cognitive Atlas took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-cogat took 3.9219162464141846s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.27504730224609375s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.022792577743530273s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007023811340332031s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-cogpo took 3.9681951999664307s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.315376281738281e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0007071495056152344s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.2659759521484375s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004019737243652344s
Believability | Calculation of trust value for Current Procedural Terminology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cpt took 4.01521635055542s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 9.34600830078125e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.31088852882385254s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.0213320255279541s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017504692077636719s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-csp took 4.186209201812744s
Availability | SPARQL endpoint availability check for COSTART took 9.322166442871094e-05s
Availability | VoID file availability check for COSTART took 0.0007932186126708984s
Completeness | Calculation of interlinking completeness for COSTART took 0.2646918296813965s
Reputation | Calculation of the PageRank for COSTART took 0.020725488662719727s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009665489196777344s
Believability | Calculation of trust value for COSTART took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-cst took 4.1129748821258545s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 8.845329284667969e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0007426738739013672s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.26258230209350586s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020671606063842773s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0004782676696777344s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ctcae took 3.9097869396209717s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 9.131431579589844e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0007712841033935547s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.2711327075958252s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.021191120147705078s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004336833953857422s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ctx took 3.865983486175537s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.4345855712890625e-05s
Availability | VoID file availability check for Dendritic cell took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.2613205909729004s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020874500274658203s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0009276866912841797s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00033974647521972656s
Believability | Calculation of trust value for Dendritic cell took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-dc_cl took 4.131486177444458s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 9.131431579589844e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.26426267623901367s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.020474910736083984s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.368492126464844e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 7.62939453125e-06s
INFO | --- Analysis for bioportal-ddanat took 4.114046812057495s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 8.916854858398438e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.2685520648956299s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020778656005859375s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0008943080902099609s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ddi took 4.30437159538269s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0008232593536376953s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.2814803123474121s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.7738037109375e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-diagnosticont took 3.9392213821411133s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.2781238555908203s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.0001537799835205078s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 3.9855477809906006s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Human disease ontology took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2667050361633301s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020641326904296875s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.000629425048828125s
Believability | Calculation of trust value for Human disease ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-doid took 3.99794340133667s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.00034427642822265625s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.2606797218322754s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.02096080780029297s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007805824279785156s
Believability | Calculation of trust value for Electrocardiography Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ecg took 3.820866107940674s
Availability | SPARQL endpoint availability check for Evidence codes took 4.267692565917969e-05s
Availability | VoID file availability check for Evidence codes took 0.00041294097900390625s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.263857364654541s
Reputation | Calculation of the PageRank for Evidence codes took 0.020575284957885742s
Interlinking | Calculation of Degree of Connection for Evidence codes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 2.9802322387695312e-05s
Believability | Calculation of trust value for Evidence codes took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-eco took 3.907902240753174s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.30815792083740234s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020925521850585938s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0016453266143798828s
Believability | Calculation of trust value for Experimental Factor Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-efo took 4.436770439147949s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 0.00010061264038085938s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0004017353057861328s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.2636139392852783s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.02095484733581543s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011200904846191406s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ehda took 3.845099449157715s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 8.749961853027344e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.2587447166442871s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.021068572998046875s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007634162902832031s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 3.814697265625e-06s
INFO | --- Analysis for bioportal-ehdaa took 3.8739612102508545s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 5.14984130859375e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.26493406295776367s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020806550979614258s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005180835723876953s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 3.9833645820617676s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.38690185546875e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.26706695556640625s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020899295806884766s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 2.86102294921875e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-emap took 4.116838216781616s
Availability | SPARQL endpoint availability check for Environment Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Environment Ontology took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.26964879035949707s
Reputation | Calculation of the PageRank for Environment Ontology took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0004024505615234375s
Believability | Calculation of trust value for Environment Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-envo took 4.015886545181274s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.601478576660156e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.2567267417907715s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020772218704223633s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0002865791320800781s
Believability | Calculation of trust value for Plant environmental conditions took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-eo took 3.8855605125427246s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.2617213726043701s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.02077174186706543s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0011439323425292969s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ep took 3.6950836181640625s
Availability | SPARQL endpoint availability check for Epilepsy took 4.315376281738281e-05s
Availability | VoID file availability check for Epilepsy took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.2606067657470703s
Reputation | Calculation of the PageRank for Epilepsy took 0.0210874080657959s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00012946128845214844s
Believability | Calculation of trust value for Epilepsy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-epileponto took 3.7219483852386475s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.553794860839844e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.256317138671875s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020941972732543945s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.001100301742553711s
Believability | Calculation of trust value for eagle-i research resource ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ero took 4.092735767364502s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.291534423828125e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.2640700340270996s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0010862350463867188s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ev took 3.8207790851593018s
Availability | SPARQL endpoint availability check for ExO took 5.8650970458984375e-05s
Availability | VoID file availability check for ExO took 0.0002999305725097656s
Completeness | Calculation of interlinking completeness for ExO took 0.26038527488708496s
Reputation | Calculation of the PageRank for ExO took 0.020742416381835938s
Interlinking | Calculation of Degree of Connection for ExO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for ExO took 0.0002357959747314453s
Believability | Calculation of trust value for ExO took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-exo took 3.7698075771331787s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 7.915496826171875e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.25782275199890137s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020771503448486328s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00010967254638671875s
Believability | Calculation of trust value for Fungal gross anatomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-fao took 3.928084373474121s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.291534423828125e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0006740093231201172s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.2592964172363281s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.021049022674560547s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00018858909606933594s
Believability | Calculation of trust value for Biological imaging methods took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fbbi took 4.1429948806762695s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 7.510185241699219e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.2664661407470703s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020918846130371094s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.00066375732421875s
Believability | Calculation of trust value for Drosophila gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fbbt took 3.9949474334716797s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.2438507080078125e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.25697970390319824s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02090764045715332s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004146099090576172s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fbcv took 3.9659297466278076s
Availability | SPARQL endpoint availability check for Drosophila development took 7.510185241699219e-05s
Availability | VoID file availability check for Drosophila development took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.26146388053894043s
Reputation | Calculation of the PageRank for Drosophila development took 0.020928621292114258s
Interlinking | Calculation of Degree of Connection for Drosophila development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.458427429199219e-05s
Believability | Calculation of trust value for Drosophila development took 3.814697265625e-06s
INFO | --- Analysis for bioportal-fbdv took 3.8987784385681152s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.291534423828125e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.2557969093322754s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020644664764404297s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.00042366981506347656s
Believability | Calculation of trust value for Fly taxonomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-fbsp took 3.9707493782043457s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 5.841255187988281e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.2586493492126465s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.021108150482177734s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.0002186298370361328s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 3.9811549186706543s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 7.557868957519531e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.26271820068359375s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020781755447387695s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.000392913818359375s
Believability | Calculation of trust value for Family Health History Ontology took 3.1948089599609375e-05s
INFO | --- Analysis for bioportal-fhho took 3.7601053714752197s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.2589268684387207s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020676374435424805s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010066032409667969s
Believability | Calculation of trust value for Influenza Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-flu took 3.7406139373779297s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 7.510185241699219e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.2602062225341797s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.02091193199157715s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.29425048828125e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fma took 4.046770095825195s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 7.295608520507812e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.25191164016723633s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020899295806884766s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00012826919555664062s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-fypo took 3.9532968997955322s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.25463223457336426s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.020867586135864258s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 8.7738037109375e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-geospecies took 5.6458234786987305s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0004220008850097656s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.25746917724609375s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00015974044799804688s
Believability | Calculation of trust value for General Formal Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-gfo took 3.8137919902801514s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.267692565917969e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.25777697563171387s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020966053009033203s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0005793571472167969s
Believability | Calculation of trust value for General Formal Ontology: Biology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-gfo-bio took 3.8340234756469727s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.291534423828125e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.2677135467529297s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.02082204818725586s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008285045623779297s
Believability | Calculation of trust value for Gene Ontology Extension took 3.814697265625e-06s
INFO | --- Analysis for bioportal-go_x1 took 3.872541666030884s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.839897155761719e-05s
Availability | VoID file availability check for Gene Ontology took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2521505355834961s
Reputation | Calculation of the PageRank for Gene Ontology took 0.0208892822265625s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008137226104736328s
Believability | Calculation of trust value for Gene Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-go_x2 took 3.750533103942871s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 7.200241088867188e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0007665157318115234s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.263049840927124s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.02115654945373535s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.123283386230469e-05s
Believability | Calculation of trust value for Cereal Plant Development took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-gro took 4.028670072555542s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 0.00016260147094726562s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0007588863372802734s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.25626659393310547s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.021068572998046875s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004184246063232422s
Believability | Calculation of trust value for Cereal plant gross anatomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-gro_x1 took 4.356793165206909s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 6.937980651855469e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2648732662200928s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02069544792175293s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007305145263671875s
Believability | Calculation of trust value for Gene Regulation Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-gro_x2 took 3.6775403022766113s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2533705234527588s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020731687545776367s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005738735198974609s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-hao took 3.7544376850128174s
Availability | SPARQL endpoint availability check for HCPCS took 4.1961669921875e-05s
Availability | VoID file availability check for HCPCS took 0.00036215782165527344s
Completeness | Calculation of interlinking completeness for HCPCS took 0.25664353370666504s
Reputation | Calculation of the PageRank for HCPCS took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00021982192993164062s
Believability | Calculation of trust value for HCPCS took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hcpcs took 3.708465576171875s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.1484832763671875e-05s
Availability | VoID file availability check for Health Level Seven took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.2559976577758789s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020841121673583984s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012507438659667969s
Believability | Calculation of trust value for Health Level Seven took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hl7 took 3.7825491428375244s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.124641418457031e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2698981761932373s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00035071372985839844s
Believability | Calculation of trust value for HEALTH_INDICATORS took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-hlth_indics took 3.9291837215423584s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 5.6743621826171875e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.3041651248931885s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.020560741424560547s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.123283386230469e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-hom took 3.9270801544189453s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.5299530029296875e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.2671656608581543s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.02086663246154785s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.218650817871094e-05s
Believability | Calculation of trust value for HOM-HARVARD took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-hom_harvard took 3.8913557529449463s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.26602602005004883s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.023549795150756836s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0010993480682373047s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0008058547973632812s
Believability | Calculation of trust value for Human Phenotype Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-hp_x1 took 3.98826003074646s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 8.535385131835938e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.2711489200592041s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.02067399024963379s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0009918212890625s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-hpio took 3.8360443115234375s
Availability | SPARQL endpoint availability check for HUGO took 4.315376281738281e-05s
Availability | VoID file availability check for HUGO took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for HUGO took 0.2669825553894043s
Reputation | Calculation of the PageRank for HUGO took 0.02289438247680664s
Interlinking | Calculation of Degree of Connection for HUGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for HUGO took 8.320808410644531e-05s
Believability | Calculation of trust value for HUGO took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-hugo took 3.789327621459961s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.273479700088501s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.02087998390197754s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006453990936279297s
Believability | Calculation of trust value for Information Artifact Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-iao took 4.098039388656616s
Availability | SPARQL endpoint availability check for ICD10 took 9.083747863769531e-05s
Availability | VoID file availability check for ICD10 took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for ICD10 took 0.276888370513916s
Reputation | Calculation of the PageRank for ICD10 took 0.02197885513305664s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0007805824279785156s
Believability | Calculation of trust value for ICD10 took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-icd10 took 3.9774458408355713s
Availability | SPARQL endpoint availability check for ICD10CM took 8.630752563476562e-05s
Availability | VoID file availability check for ICD10CM took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.26346254348754883s
Reputation | Calculation of the PageRank for ICD10CM took 0.021606922149658203s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0005958080291748047s
Believability | Calculation of trust value for ICD10CM took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-icd10cm took 3.8577773571014404s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.315376281738281e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.2624490261077881s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.02194952964782715s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00015020370483398438s
Believability | Calculation of trust value for ICD-10-PCS took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-icd10pcs took 3.781916618347168s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.124641418457031e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.26767754554748535s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020951271057128906s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006272792816162109s
Believability | Calculation of trust value for International Classification of Diseases took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-icd9cm took 3.7993760108947754s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.363059997558594e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.26471424102783203s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020668506622314453s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004360675811767578s
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 3.7696192264556885s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 8.416175842285156e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.26299214363098145s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02137470245361328s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.001199960708618164s
Believability | Calculation of trust value for International Classification for Nursing Practice took 7.62939453125e-06s
INFO | --- Analysis for bioportal-icnp took 3.8547983169555664s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.363059997558594e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.26288819313049316s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.02147960662841797s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004322528839111328s
Believability | Calculation of trust value for International Classification of Primary Care took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icpc took 3.9948031902313232s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 5.5789947509765625e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.27196502685546875s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008115768432617188s
Believability | Calculation of trust value for ICPC-2 PLUS took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-icpc2p took 3.8213789463043213s
Availability | SPARQL endpoint availability check for ICPS Network took 4.410743713378906e-05s
Availability | VoID file availability check for ICPS Network took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.2688791751861572s
Reputation | Calculation of the PageRank for ICPS Network took 0.021989107131958008s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0002162456512451172s
Believability | Calculation of trust value for ICPS Network took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-icps took 3.845628499984741s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.27107691764831543s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020841121673583984s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008091926574707031s
Believability | Calculation of trust value for Infectious Disease Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-ido took 4.289222240447998s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 0.00011682510375976562s
Availability | VoID file availability check for Brucellosis Ontology took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2665269374847412s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020519495010375977s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0010907649993896484s
Believability | Calculation of trust value for Brucellosis Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-idobru took 3.7631771564483643s
Availability | SPARQL endpoint availability check for Malaria Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.27329230308532715s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.021680355072021484s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0012402534484863281s
Believability | Calculation of trust value for Malaria Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-idomal took 4.028707981109619s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 9.298324584960938e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.2637622356414795s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.021085500717163086s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003154277801513672s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-iev took 4.1064064502716064s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.291534423828125e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.26517605781555176s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020865201950073242s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00015282630920410156s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-imgt took 3.93729829788208s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.5299530029296875e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.2681593894958496s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.02096700668334961s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0004992485046386719s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-imr took 4.095242738723755s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.2699282169342041s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.021093368530273438s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007693767547607422s
Believability | Calculation of trust value for Interaction Network Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ino took 4.0463621616363525s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.2438507080078125e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2699754238128662s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.02226543426513672s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 2.9802322387695312e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-invertebrata took 3.8798491954803467s
Availability | SPARQL endpoint availability check for IxnO took 8.749961853027344e-05s
Availability | VoID file availability check for IxnO took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for IxnO took 0.26273322105407715s
Reputation | Calculation of the PageRank for IxnO took 0.020760536193847656s
Interlinking | Calculation of Degree of Connection for IxnO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.0001857280731201172s
Believability | Calculation of trust value for IxnO took 7.62939453125e-06s
INFO | --- Analysis for bioportal-ixno took 3.8934566974639893s
Availability | SPARQL endpoint availability check for SysMO-JERM took 8.606910705566406e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.2681136131286621s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020872831344604492s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.00038933753967285156s
Believability | Calculation of trust value for SysMO-JERM took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-jerm took 4.197909116744995s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 9.274482727050781e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.26319146156311035s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.021184921264648438s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-kisao took 3.7894344329833984s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 8.7738037109375e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.2717399597167969s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.021127700805664062s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00019502639770507812s
Believability | Calculation of trust value for Loggerhead nesting took 7.62939453125e-06s
INFO | --- Analysis for bioportal-lhn took 3.953518867492676s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.26372766494750977s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.021082639694213867s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00022268295288085938s
Believability | Calculation of trust value for Lipid Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-lipro took 3.9600231647491455s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 6.246566772460938e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.001211404800415039s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.3090827465057373s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.02091217041015625s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0017576217651367188s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-lnc took 4.414979696273804s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 5.5789947509765625e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2732720375061035s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006299018859863281s
Believability | Calculation of trust value for Mouse adult gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ma took 3.8518848419189453s
Availability | SPARQL endpoint availability check for Multiple alignment took 9.202957153320312e-05s
Availability | VoID file availability check for Multiple alignment took 0.0008151531219482422s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.2718832492828369s
Reputation | Calculation of the PageRank for Multiple alignment took 0.021068811416625977s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00021767616271972656s
Believability | Calculation of trust value for Multiple alignment took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mao took 4.116903066635132s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.220008850097656e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.000637054443359375s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.26451969146728516s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.021715402603149414s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006737709045410156s
Believability | Calculation of trust value for Minimal anatomical terminology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mat took 4.049709796905518s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 8.916854858398438e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.2631053924560547s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020630598068237305s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004279613494873047s
Believability | Calculation of trust value for Breast tissue cell lines took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mcbcc took 3.9232242107391357s
Availability | SPARQL endpoint availability check for Cell line ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2632482051849365s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007212162017822266s
Believability | Calculation of trust value for Cell line ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mccl took 3.831573963165283s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Cell line ontology took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2632584571838379s
Reputation | Calculation of the PageRank for Cell line ontology took 0.021680593490600586s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0013709068298339844s
Believability | Calculation of trust value for Cell line ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 3.9439046382904053s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 8.940696716308594e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.26503801345825195s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.02248692512512207s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00022649765014648438s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mcv took 3.820012331008911s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.315376281738281e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.27014636993408203s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.02201080322265625s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.0001761913299560547s
Believability | Calculation of trust value for Master Drug Data Base took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mddb took 4.066035032272339s
Availability | SPARQL endpoint availability check for MedDRA took 9.107589721679688e-05s
Availability | VoID file availability check for MedDRA took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for MedDRA took 0.2716941833496094s
Reputation | Calculation of the PageRank for MedDRA took 0.020906925201416016s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.001085519790649414s
Believability | Calculation of trust value for MedDRA took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mdr took 3.8270723819732666s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.291534423828125e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.27628564834594727s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02217698097229004s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008592605590820312s
Believability | Calculation of trust value for MedlinePlus Health Topics took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-medlineplus took 3.906691312789917s
Availability | SPARQL endpoint availability check for MeGO took 9.632110595703125e-05s
Availability | VoID file availability check for MeGO took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for MeGO took 0.26352930068969727s
Reputation | Calculation of the PageRank for MeGO took 0.02289581298828125s
Interlinking | Calculation of Degree of Connection for MeGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014400482177734375s
Believability | Calculation of trust value for MeGO took 2.2649765014648438e-05s
INFO | --- Analysis for bioportal-mego took 3.771162986755371s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 5.555152893066406e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.00041556358337402344s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.3123009204864502s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.021170616149902344s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018172264099121094s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mesh-owl took 4.2012269496917725s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.2639157772064209s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.022658586502075195s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0005953311920166016s
Believability | Calculation of trust value for Mental Functioning Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mf took 3.7740559577941895s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 8.678436279296875e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.26287174224853516s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005435943603515625s
Believability | Calculation of trust value for Medaka fish anatomy and development took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mfo took 3.9170143604278564s
Availability | SPARQL endpoint availability check for Emotion Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2662997245788574s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.02260446548461914s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007231235504150391s
Believability | Calculation of trust value for Emotion Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mfoem took 3.816993236541748s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 0.000102996826171875s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.26856017112731934s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010704994201660156s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-mhc took 4.011659860610962s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.315376281738281e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.264514684677124s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.02120661735534668s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0008268356323242188s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0007061958312988281s
Believability | Calculation of trust value for Protein-protein interaction took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mi took 3.889761447906494s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.2438507080078125e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.255037784576416s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.021268844604492188s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0006928443908691406s
Believability | Calculation of trust value for Mosquito insecticide resistance took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-miro took 3.9092273712158203s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.2608027458190918s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.021160125732421875s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001399517059326172s
Believability | Calculation of trust value for Measurement Method Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mmo took 3.718827247619629s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for MGED Ontology took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.25844788551330566s
Reputation | Calculation of the PageRank for MGED Ontology took 0.021291017532348633s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003733634948730469s
Believability | Calculation of trust value for MGED Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-mo took 3.6966426372528076s
Availability | SPARQL endpoint availability check for Protein modification took 4.38690185546875e-05s
Availability | VoID file availability check for Protein modification took 0.0007350444793701172s
Completeness | Calculation of interlinking completeness for Protein modification took 0.2615547180175781s
Reputation | Calculation of the PageRank for Protein modification took 0.021044015884399414s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00021696090698242188s
Believability | Calculation of trust value for Protein modification took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mod took 4.338196039199829s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 8.344650268554688e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.2606496810913086s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.02126455307006836s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006403923034667969s
Believability | Calculation of trust value for Mammalian phenotype took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mp took 3.9813544750213623s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.1961669921875e-05s
Availability | VoID file availability check for Mouse pathology took 0.0003993511199951172s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.2575874328613281s
Reputation | Calculation of the PageRank for Mouse pathology took 0.021015405654907227s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004756450653076172s
Believability | Calculation of trust value for Mouse pathology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-mpath took 3.8492774963378906s
Availability | SPARQL endpoint availability check for Mass spectrometry took 8.440017700195312e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0003693103790283203s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.2681539058685303s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.02101302146911621s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003509521484375s
Believability | Calculation of trust value for Mass spectrometry took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ms took 3.69193434715271s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.124641418457031e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.31496524810791016s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.0207669734954834s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018036365509033203s
Believability | Calculation of trust value for Medical Subject Headings took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-msh took 4.086065053939819s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.172325134277344e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.26396918296813965s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.02110433578491211s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00017142295837402344s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-mthch took 3.732698917388916s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.26004910469055176s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.02076578140258789s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007708072662353516s
Believability | Calculation of trust value for Natural Products Ontology took 1.4543533325195312e-05s
INFO | --- Analysis for bioportal-natpro took 3.6519291400909424s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 5.698204040527344e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.00054931640625s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2646942138671875s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020777225494384766s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0007839202880859375s
Believability | Calculation of trust value for NCBI organismal classification took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 3.611981153488159s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.30564308166503906s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0018854141235351562s
Believability | Calculation of trust value for NCI Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ncit took 4.332278251647949s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.291534423828125e-05s
Availability | VoID file availability check for National Drug Data File took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.26105213165283203s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020818233489990234s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006110668182373047s
Believability | Calculation of trust value for National Drug Data File took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-nddf took 3.8374807834625244s
Availability | SPARQL endpoint availability check for National Drug File took 4.172325134277344e-05s
Availability | VoID file availability check for National Drug File took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for National Drug File took 0.265857458114624s
Reputation | Calculation of the PageRank for National Drug File took 0.021037578582763672s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012688636779785156s
Believability | Calculation of trust value for National Drug File took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-ndfrt took 3.7507107257843018s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.3392181396484375e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.2688605785369873s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02113056182861328s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011262893676757812s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 4.158610820770264s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.25783753395080566s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.02176523208618164s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0007245540618896484s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-neomark took 3.8912031650543213s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0003941059112548828s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.2754204273223877s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020912885665893555s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00013327598571777344s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-neomarkontology took 3.731654405593872s
Availability | SPARQL endpoint availability check for NIFSTD took 9.107589721679688e-05s
Availability | VoID file availability check for NIFSTD took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.31634092330932617s
Reputation | Calculation of the PageRank for NIFSTD took 0.020961284637451172s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0018303394317626953s
Believability | Calculation of trust value for NIFSTD took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nif took 4.305204391479492s
Availability | SPARQL endpoint availability check for NIF Cell took 4.291534423828125e-05s
Availability | VoID file availability check for NIF Cell took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.32582640647888184s
Reputation | Calculation of the PageRank for NIF Cell took 0.020734071731567383s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0012917518615722656s
Believability | Calculation of trust value for NIF Cell took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nif_cell took 3.798917293548584s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.267692565917969e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0003936290740966797s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.25769901275634766s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.021158695220947266s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0013887882232666016s
Believability | Calculation of trust value for NIF Dysfunction took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 4.5282087326049805s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.25804877281188965s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.020816564559936523s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005495548248291016s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nigo took 3.7540130615234375s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.3392181396484375e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0003662109375s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.2653489112854004s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020635128021240234s
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.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005404949188232422s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nmr took 3.731442451477051s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0003879070281982422s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.26449060440063477s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.02100372314453125s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00011920928955078125s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nonrctontology took 3.723555088043213s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0004088878631591797s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.2630941867828369s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020824193954467773s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011749267578125s
Believability | Calculation of trust value for NanoParticle Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-npo took 4.029809951782227s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.267692565917969e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0003972053527832031s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.25988245010375977s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020900964736938477s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007276535034179688s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-oae took 4.064496278762817s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 5.054473876953125e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.26049113273620605s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.021055936813354492s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0013968944549560547s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-obi took 4.007697343826294s
Availability | SPARQL endpoint availability check for OBOE took 4.220008850097656e-05s
Availability | VoID file availability check for OBOE took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for OBOE took 0.2547948360443115s
Reputation | Calculation of the PageRank for OBOE took 0.020950794219970703s
Interlinking | Calculation of Degree of Connection for OBOE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011491775512695312s
Believability | Calculation of trust value for OBOE took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-oboe took 4.076374530792236s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.220008850097656e-05s
Availability | VoID file availability check for OBOE SBC took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.25459790229797363s
Reputation | Calculation of the PageRank for OBOE SBC took 0.0209808349609375s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007615089416503906s
Believability | Calculation of trust value for OBOE SBC took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 3.949953556060791s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.267692565917969e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0008714199066162109s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2734835147857666s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020701169967651367s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005598068237304688s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ocre took 3.883415699005127s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 8.559226989746094e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.00038433074951171875s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.2651708126068115s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.02113962173461914s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008172988891601562s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-odgi took 3.8777477741241455s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.267692565917969e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0003910064697265625s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2564370632171631s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.02076888084411621s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008420944213867188s
Believability | Calculation of trust value for Ontology for Genetic Interval took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ogi took 3.710587978363037s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.2660512924194336s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00028514862060546875s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ogmd took 3.87945294380188s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 9.322166442871094e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.2600216865539551s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.02133774757385254s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006597042083740234s
Believability | Calculation of trust value for Ontology for General Medical Science took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ogms took 3.770740509033203s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.291534423828125e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.26044201850891113s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020831584930419922s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.001138448715209961s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-omim took 3.6612939834594727s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.220008850097656e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.257765531539917s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020966529846191406s
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.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.00036907196044921875s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-omit took 3.9071106910705566s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0003070831298828125s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.2666282653808594s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005850791931152344s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-omrse took 2.3555212020874023s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.267763614654541s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007660388946533203s
Believability | Calculation of trust value for Ontology of Data Mining took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ontodm took 3.8114571571350098s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.25859737396240234s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00023126602172851562s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ontodt took 3.9784862995147705s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.267692565917969e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0007243156433105469s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.26319026947021484s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020734071731567383s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006084442138671875s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ontoorpha took 3.8775041103363037s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.2611832618713379s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020827770233154297s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0008771419525146484s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-opl took 3.724877119064331s
Availability | SPARQL endpoint availability check for Phenotypic quality took 6.365776062011719e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.2704761028289795s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.0216982364654541s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008690357208251953s
Believability | Calculation of trust value for Phenotypic quality took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pato took 3.8878917694091797s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.2438507080078125e-05s
Availability | VoID file availability check for Physician Data Query took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.2667539119720459s
Reputation | Calculation of the PageRank for Physician Data Query took 0.02986288070678711s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0010561943054199219s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0010213851928710938s
Believability | Calculation of trust value for Physician Data Query took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pdq took 3.984358787536621s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 8.463859558105469e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.26667213439941406s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.022550106048583984s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007522106170654297s
Believability | Calculation of trust value for Pediatric Terminology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pedterm took 3.8599324226379395s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 5.53131103515625e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.26732969284057617s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020921707153320312s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.0001938343048095703s
Believability | Calculation of trust value for Parasite Experiment Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-peo took 3.799564838409424s
Availability | SPARQL endpoint availability check for PHARE took 8.535385131835938e-05s
Availability | VoID file availability check for PHARE took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for PHARE took 0.2721998691558838s
Reputation | Calculation of the PageRank for PHARE took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for PHARE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006213188171386719s
Believability | Calculation of trust value for PHARE took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-phare took 3.6808979511260986s
Availability | SPARQL endpoint availability check for PKO_Re took 8.416175842285156e-05s
Availability | VoID file availability check for PKO_Re took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.26934313774108887s
Reputation | Calculation of the PageRank for PKO_Re took 0.021402597427368164s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0001678466796875s
Believability | Calculation of trust value for PKO_Re took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-pko took 3.7312965393066406s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.1961669921875e-05s
Availability | VoID file availability check for PMA 2010 took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.2643108367919922s
Reputation | Calculation of the PageRank for PMA 2010 took 0.02096104621887207s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0008609294891357422s
Believability | Calculation of trust value for PMA 2010 took 7.62939453125e-06s
INFO | --- Analysis for bioportal-pma took 3.9620089530944824s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 8.559226989746094e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.00054931640625s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.26379942893981934s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020781755447387695s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00016617774963378906s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 7.62939453125e-06s
INFO | --- Analysis for bioportal-pmr took 3.887408971786499s
Availability | SPARQL endpoint availability check for Plant Anatomy took 9.298324584960938e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0008409023284912109s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.26967406272888184s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.021573781967163086s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0004799365997314453s
Believability | Calculation of trust value for Plant Anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-po took 3.9185407161712646s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 8.893013000488281e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.26702022552490234s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.022047996520996094s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007011890411376953s
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 8.58306884765625e-06s
INFO | --- Analysis for bioportal-po_x1 took 3.7867183685302734s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Plant Ontology took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.2631654739379883s
Reputation | Calculation of the PageRank for Plant Ontology took 0.025183677673339844s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0009353160858154297s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0005409717559814453s
Believability | Calculation of trust value for Plant Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-po_x2 took 3.840527057647705s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 8.726119995117188e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.2661857604980469s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020792007446289062s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006356239318847656s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 7.62939453125e-06s
INFO | --- Analysis for bioportal-pr took 3.7569103240966797s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 8.606910705566406e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.00035691261291503906s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2627220153808594s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.02115917205810547s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002529621124267578s
Believability | Calculation of trust value for Proteomics data and process provenance took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-propreo took 3.899055242538452s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Pathway ontology took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.264423131942749s
Reputation | Calculation of the PageRank for Pathway ontology took 0.021120786666870117s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012230873107910156s
Believability | Calculation of trust value for Pathway ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-pw took 3.872128486633301s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 8.416175842285156e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.26320528984069824s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020816326141357422s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-qibo took 3.9989354610443115s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.887580871582031e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0008234977722167969s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3097376823425293s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.021045684814453125s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017216205596923828s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-rcd took 4.605638027191162s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 9.369850158691406e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0010859966278076172s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.27066493034362793s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.022086620330810547s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.0001251697540283203s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-rctontology took 5.088212251663208s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.268202543258667s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.02141880989074707s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 0.00010895729064941406s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-repo took 3.7857587337493896s
Availability | SPARQL endpoint availability check for Physico-chemical process took 8.821487426757812e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0007719993591308594s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.26233744621276855s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020492076873779297s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00019025802612304688s
Believability | Calculation of trust value for Physico-chemical process took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-rex took 3.769442319869995s
Availability | SPARQL endpoint availability check for RadLex took 8.821487426757812e-05s
Availability | VoID file availability check for RadLex took 0.0007476806640625s
Completeness | Calculation of interlinking completeness for RadLex took 0.266416072845459s
Reputation | Calculation of the PageRank for RadLex took 0.02151203155517578s
Interlinking | Calculation of Degree of Connection for RadLex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RadLex took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0014553070068359375s
Believability | Calculation of trust value for RadLex took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-rid took 3.7704405784606934s
Availability | SPARQL endpoint availability check for RNA ontology took 8.606910705566406e-05s
Availability | VoID file availability check for RNA ontology took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2694277763366699s
Reputation | Calculation of the PageRank for RNA ontology took 0.021839380264282227s
Interlinking | Calculation of Degree of Connection for RNA ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005249977111816406s
Believability | Calculation of trust value for RNA ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-rnao took 3.880387783050537s
Availability | SPARQL endpoint availability check for Role Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Role Ontology took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2644214630126953s
Reputation | Calculation of the PageRank for Role Ontology took 0.020719528198242188s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00019097328186035156s
Believability | Calculation of trust value for Role Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-roleo took 3.788590669631958s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.26297831535339355s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020730257034301758s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00017786026000976562s
Believability | Calculation of trust value for Rat Strain Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-rs took 3.985780715942383s
Availability | SPARQL endpoint availability check for RxNORM took 9.012222290039062e-05s
Availability | VoID file availability check for RxNORM took 0.0007672309875488281s
Completeness | Calculation of interlinking completeness for RxNORM took 0.26852941513061523s
Reputation | Calculation of the PageRank for RxNORM took 0.02206110954284668s
Interlinking | Calculation of Degree of Connection for RxNORM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RxNORM took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0005979537963867188s
Believability | Calculation of trust value for RxNORM took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-rxnorm took 3.8361408710479736s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 9.036064147949219e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.26183104515075684s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0009868144989013672s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sao took 3.8917183876037598s
Availability | SPARQL endpoint availability check for Systems Biology took 8.606910705566406e-05s
Availability | VoID file availability check for Systems Biology took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.2750980854034424s
Reputation | Calculation of the PageRank for Systems Biology took 0.020679712295532227s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004429817199707031s
Believability | Calculation of trust value for Systems Biology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-sbo took 3.9132509231567383s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0006103515625s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.2633223533630371s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02229905128479004s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010943412780761719s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-sbro took 3.931894302368164s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.2709667682647705s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.021640777587890625s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0012929439544677734s
Believability | Calculation of trust value for Sleep Domain Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-sdo took 3.927717924118042s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.57763671875e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0007052421569824219s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.272205114364624s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02147650718688965s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003497600555419922s
Believability | Calculation of trust value for Sample processing and separation techniques took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-sep took 4.966905117034912s
Availability | SPARQL endpoint availability check for Student Health Record took 8.7738037109375e-05s
Availability | VoID file availability check for Student Health Record took 0.0007412433624267578s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.26422905921936035s
Reputation | Calculation of the PageRank for Student Health Record took 0.02087235450744629s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0009765625s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0005390644073486328s
Believability | Calculation of trust value for Student Health Record took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-shr took 4.023152589797974s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0007469654083251953s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.2695770263671875s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0011508464813232422s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sio took 4.707976341247559s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 6.008148193359375e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.28461551666259766s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.02095198631286621s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00019598007202148438s
Believability | Calculation of trust value for Situation-Based Access Control took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-sitbac took 4.080385446548462s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 8.821487426757812e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3120121955871582s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.022481441497802734s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.001909017562866211s
Believability | Calculation of trust value for SNOMED Clinical Terms took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-snomedct took 4.112972974777222s
Availability | SPARQL endpoint availability check for SNP-Ontology took 9.465217590332031e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.2643094062805176s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.02052474021911621s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006661415100097656s
Believability | Calculation of trust value for SNP-Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-snpo took 4.171516418457031s
Availability | SPARQL endpoint availability check for Sequence types and features took 8.654594421386719e-05s
Availability | VoID file availability check for Sequence types and features took 0.0008203983306884766s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.27359604835510254s
Reputation | Calculation of the PageRank for Sequence types and features took 0.02112293243408203s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005643367767333984s
Believability | Calculation of trust value for Sequence types and features took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-so_x1 took 4.06097412109375s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 0.00010991096496582031s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.3186914920806885s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.023240327835083008s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0011162757873535156s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0017180442810058594s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-sopharm took 4.464046001434326s
Availability | SPARQL endpoint availability check for SoyOntology took 9.012222290039062e-05s
Availability | VoID file availability check for SoyOntology took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.26508045196533203s
Reputation | Calculation of the PageRank for SoyOntology took 0.021458864212036133s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00012540817260742188s
Believability | Calculation of trust value for SoyOntology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-soy took 3.7614731788635254s
Availability | SPARQL endpoint availability check for Spider Ontology took 8.487701416015625e-05s
Availability | VoID file availability check for Spider Ontology took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.27345967292785645s
Reputation | Calculation of the PageRank for Spider Ontology took 0.02164149284362793s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00036644935607910156s
Believability | Calculation of trust value for Spider Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-spd took 3.730833053588867s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2628295421600342s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.021149873733520508s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0002682209014892578s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-spto took 3.846285104751587s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 8.320808410644531e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.27065587043762207s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004374980926513672s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-sso took 3.862025737762451s
Availability | SPARQL endpoint availability check for Software Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Software Ontology took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.2699747085571289s
Reputation | Calculation of the PageRank for Software Ontology took 0.023000478744506836s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0003921985626220703s
Believability | Calculation of trust value for Software Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-swo took 3.8508496284484863s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 9.560585021972656e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.27118635177612305s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0009596347808837891s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002887248992919922s
Believability | Calculation of trust value for Tick gross anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-tads took 5.708224773406982s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0007252693176269531s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.2661733627319336s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.021293163299560547s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008645057678222656s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-tao took 3.8282933235168457s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 8.726119995117188e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.2737252712249756s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.021694660186767578s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.726119995117188e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-taxrank took 3.9140589237213135s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 5.6743621826171875e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0007827281951904297s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.2706432342529297s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.022124767303466797s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.534027099609375e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-teddy took 4.214158773422241s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.935264587402344e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.2812662124633789s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.02138972282409668s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008480548858642578s
Believability | Calculation of trust value for Time Event Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-teo took 4.084824323654175s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.267692565917969e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.26818323135375977s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0003905296325683594s
Believability | Calculation of trust value for Mosquito gross anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-tgma took 3.8786168098449707s
Availability | SPARQL endpoint availability check for thesaurus took 8.440017700195312e-05s
Availability | VoID file availability check for thesaurus took 0.0008902549743652344s
Completeness | Calculation of interlinking completeness for thesaurus took 0.26821351051330566s
Reputation | Calculation of the PageRank for thesaurus took 0.021208763122558594s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.866455078125e-05s
Believability | Calculation of trust value for thesaurus took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-thesaurus took 4.030345439910889s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 8.630752563476562e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.27509379386901855s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.02129387855529785s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.00034546852111816406s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 3.9511349201202393s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.2630174160003662s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.02252507209777832s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0007903575897216797s
Believability | Calculation of trust value for Translational Medicine Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-tmo took 3.829272747039795s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 0.00011515617370605469s
Availability | VoID file availability check for Plant Trait Ontology took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.26416563987731934s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020884037017822266s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00017952919006347656s
Believability | Calculation of trust value for Plant Trait Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-to took 4.2659592628479s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.262676477432251s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.02083277702331543s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0009624958038330078s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00024127960205078125s
Believability | Calculation of trust value for TOK_Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-tok took 4.120259523391724s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 0.00011754035949707031s
Availability | VoID file availability check for Teleost taxonomy took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.26943254470825195s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020686864852905273s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00018787384033203125s
Believability | Calculation of trust value for Teleost taxonomy took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-tto took 3.841143846511841s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 0.00011205673217773438s
Availability | VoID file availability check for Uber anatomy ontology took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.2661867141723633s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0009984970092773438s
Believability | Calculation of trust value for Uber anatomy ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-uberon took 4.010680437088013s
Availability | SPARQL endpoint availability check for Units Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Units Ontology took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.2617213726043701s
Reputation | Calculation of the PageRank for Units Ontology took 0.021090984344482422s
Interlinking | Calculation of Degree of Connection for Units Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Units Ontology took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002110004425048828s
Believability | Calculation of trust value for Units Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-unitsontology took 3.6800484657287598s
Availability | SPARQL endpoint availability check for Units of measurement took 8.654594421386719e-05s
Availability | VoID file availability check for Units of measurement took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.2815418243408203s
Reputation | Calculation of the PageRank for Units of measurement took 0.02093362808227539s
Interlinking | Calculation of Degree of Connection for Units of measurement took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.000286102294921875s
Believability | Calculation of trust value for Units of measurement took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-uo took 4.2003960609436035s
Availability | SPARQL endpoint availability check for VANDF took 8.893013000488281e-05s
Availability | VoID file availability check for VANDF took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for VANDF took 0.2660825252532959s
Reputation | Calculation of the PageRank for VANDF took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for VANDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for VANDF took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006608963012695312s
Believability | Calculation of trust value for VANDF took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vandf took 3.9941389560699463s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 5.5789947509765625e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0003170967102050781s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2652153968811035s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.02073836326599121s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00041103363037109375s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-vao took 4.251506090164185s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.9114227294921875e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.2562863826751709s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006122589111328125s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vhog took 4.017019271850586s
Availability | SPARQL endpoint availability check for VIVO took 4.100799560546875e-05s
Availability | VoID file availability check for VIVO took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for VIVO took 0.26561546325683594s
Reputation | Calculation of the PageRank for VIVO took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for VIVO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.00038433074951171875s
Believability | Calculation of trust value for VIVO took 3.814697265625e-06s
INFO | --- Analysis for bioportal-vivo took 3.799182653427124s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0011053085327148438s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.25472569465637207s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.02036428451538086s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.001171112060546875s
Believability | Calculation of trust value for Vaccine Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-vo took 3.8672380447387695s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.2686426639556885s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020522594451904297s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00023031234741210938s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-vt took 3.8009440898895264s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 0.00010466575622558594s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.2542867660522461s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.02044510841369629s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005018711090087891s
Believability | Calculation of trust value for C. elegans gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-wbbt took 3.7271230220794678s
Availability | SPARQL endpoint availability check for C. elegans development took 4.1961669921875e-05s
Availability | VoID file availability check for C. elegans development took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.26171374320983887s
Reputation | Calculation of the PageRank for C. elegans development took 0.0204770565032959s
Interlinking | Calculation of Degree of Connection for C. elegans development took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for C. elegans development took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.267692565917969e-05s
Believability | Calculation of trust value for C. elegans development took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-wbls took 3.6851961612701416s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.1484832763671875e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.00040793418884277344s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.25937366485595703s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.606910705566406e-05s
Believability | Calculation of trust value for C. elegans phenotype took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-wbphenotype took 3.75819730758667s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 7.677078247070312e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.2623469829559326s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.021770238876342773s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005681514739990234s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-who took 3.933213233947754s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.2438507080078125e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2680516242980957s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.021741867065429688s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006585121154785156s
Believability | Calculation of trust value for Xenopus anatomy and development took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-xao took 3.9658007621765137s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.744529724121094e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.2627875804901123s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.02061152458190918s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00022840499877929688s
Believability | Calculation of trust value for Experimental Conditions Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-xco took 3.7813327312469482s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 8.749961853027344e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.26741647720336914s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020871639251708984s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00025463104248046875s
Believability | Calculation of trust value for Yeast phenotypes took 7.62939453125e-06s
INFO | --- Analysis for bioportal-ypo took 3.7664380073547363s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 9.202957153320312e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.26903724670410156s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.02137446403503418s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007464885711669922s
Believability | Calculation of trust value for Zebrafish anatomy and development took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-zfa took 3.7719240188598633s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 8.678436279296875e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0012857913970947266s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.27293968200683594s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.022142410278320312s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0011141300201416016s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 3.814697265625e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.1444091796875e-05s
INFO | --- Analysis for Bioportal_link took 3.689673900604248s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.37515974044799805s
Availability | VoID file availability check for BioSamples RDF took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.272918701171875s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.1948089599609375e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.2159347534179688e-05s
INFO | --- Analysis for biosamples-rdf took 3.4128963947296143s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.07719182968139648s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.26256465911865234s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.021106481552124023s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.0001220703125s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for bis-linked-data took 2.5007898807525635s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 8.702278137207031e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.26405954360961914s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020743846893310547s
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.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.029273986816406e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.1205673217773438e-05s
INFO | --- Analysis for bll-thesaurus took 3.41530442237854s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.2109456062316895s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.26454973220825195s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.022119998931884766s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.461143493652344e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.049041748046875e-05s
INFO | --- Analysis for bluk-bnb took 11.647419691085815s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.30263352394104004s
Availability | VoID file availability check for Thesaurus BNCF took 0.0005781650543212891s
Extra | Recovery of all triples for Thesaurus BNCF took 46.909218072891235s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6098642349243164s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6565654277801514s
Interoperability | New terms check for Thesaurus BNCF took 1.468956708908081s
Versatility | Languages check for Thesaurus BNCF took 6.568650960922241s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.8817126750946045s
Security | Check HTTPS for Thesaurus BNCF took 0.08620500564575195s
Interpretability | RDF structures check for Thesaurus BNCF took 0.10636472702026367s
Versatility | Serialization formats check for Thesaurus BNCF took 0.10807609558105469s
Availability | RDF dump link check for Thesaurus BNCF took 0.10927844047546387s
License | MR license check for Thesaurus BNCF took 0.10628819465637207s
License | HR license check for Thesaurus BNCF took 0.1834559440612793s
Amount of data | Number of property check for Thesaurus BNCF took 0.10529351234436035s
Understandability | Number of label check for Thesaurus BNCF took 0.24273324012756348s
Understandability | URI regex check for Thesaurus BNCF took 0.20929813385009766s
Understandability | Vocabs check for Thesaurus BNCF took 0.10651922225952148s
Verifiability | Authors check for Thesaurus BNCF took 0.10737371444702148s
Verifiability | Publishers check for Thesaurus BNCF took 0.1104421615600586s
Performance | Throughput check for Thesaurus BNCF took 10.746479988098145s
Amount of data | Check the number of entities for Thesaurus BNCF took 3.600120544433594e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.10497736930847168s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.1044011116027832s
Interlinking | skos check for Thesaurus BNCF took 0.16756200790405273s
Interlinking | skos check for Thesaurus BNCF took 0.13405632972717285s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.14266419410705566s
Currency | Creation date check for Thesaurus BNCF took 0.21508002281188965s
Currency | Modification date check for Thesaurus BNCF took 0.20789384841918945s
Rep.Conc. | URIs length for Thesaurus BNCF took 24.119635820388794s
Interoperability | New vocabularies check for Thesaurus BNCF took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.15163373947143555s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.1031184196472168s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.10560870170593262s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 11.50846004486084s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.4877641201019287s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.850929021835327s
Consistency | Disjoint class check for Thesaurus BNCF took 0.11031675338745117s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.8970189094543457s
Consistency | Misplaced classes for Thesaurus BNCF took 6.570566177368164s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 7.273129940032959s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4133665561676025s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.238985538482666s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.3498952388763428s
Security | Sign check for Thesaurus BNCF took 0.10598373413085938s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 20.765769004821777s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.2824821472167969s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.319450378417969e-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.2159347534179688e-05s
INFO | --- Analysis for bncf-ns took 179.83048558235168s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5689740180969238s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006918907165527344s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.2561922073364258s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6821320056915283s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.675219535827637s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.93371319770813s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.240254163742065s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.372398853302002s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2736325263977051s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3849983215332031s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.46892666816711426s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.43439698219299316s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5791945457458496s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.20003366470337s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3276941776275635s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.9226818084716797s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6835265159606934s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4307246208190918s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.49646449089050293s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.34757065773010254s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.285165548324585s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.343292236328125e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3631589412689209s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3805201053619385s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.34378910064697266s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.33119654655456543s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.42143678665161133s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6923227310180664s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3594493865966797s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.80542278289795s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3576700687408447s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3365137577056885s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.32741379737854004s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6908853054046631s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03053736686706543s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.027411460876464844s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.361522912979126s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.723076581954956s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.42040467262268066s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.122119188308716s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.526315450668335s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.744668006896973s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030032873153686523s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36922764778137207s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3399217128753662s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.430738925933838s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3220088481903076s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0217740535736084s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.00010251998901367188s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 9.989738464355469e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6689300537109375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1444091796875e-05s
INFO | --- Analysis for bpr took 386.3460729122162s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 8.869171142578125e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.2704324722290039s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020904541015625s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.176399230957031e-05s
Believability | Calculation of trust value for Brazilian Politicians took 8.106231689453125e-06s
INFO | --- Analysis for brazilian-politicians took 2.527427911758423s
Availability | SPARQL endpoint availability check for Bricklink took 1.4563891887664795s
Availability | VoID file availability check for Bricklink took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Bricklink took 0.28374409675598145s
Reputation | Calculation of the PageRank for Bricklink took 0.02118062973022461s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.747245788574219e-05s
Believability | Calculation of trust value for Bricklink took 1.0013580322265625e-05s
INFO | --- Analysis for bricklink took 9.2971031665802s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.214194774627686s
Availability | VoID file availability check for British Museum Collection took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.2837352752685547s
Reputation | Calculation of the PageRank for British Museum Collection took 0.02086186408996582s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.1948089599609375e-05s
Believability | Calculation of trust value for British Museum Collection took 9.298324584960938e-06s
INFO | --- Analysis for british-museum-collection took 72.83238506317139s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.3392181396484375e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.3195979595184326s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 5.364418029785156e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.0251998901367188e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.523754596710205s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.19113469123840332s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0005331039428710938s
Extra | Recovery of all triples for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.771665334701538s
Performance | Total latancy measurement for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.5598440170288086s
Amount of data | Number of triples check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.0217933654785156s
Interoperability | New terms check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.7354583740234375s
Versatility | Languages check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.559712886810303s
Interpretability | Number of blank nodes check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.8533565998077393s
Interpretability | RDF structures check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1153707504272461s
Versatility | Serialization formats check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11417269706726074s
Availability | RDF dump link check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11232447624206543s
License | MR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11294198036193848s
License | HR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 17.195913314819336s
Amount of data | Number of property check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11405181884765625s
Understandability | Number of label check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.18574976921081543s
Understandability | URI regex check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.22510933876037598s
Understandability | Vocabs check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11257004737854004s
Verifiability | Authors check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11319112777709961s
Verifiability | Publishers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11271119117736816s
Performance | Throughput check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.154616355895996s
Amount of data | Check the number of entities for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.510185241699219e-05s
Verifiability | Contribs. check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11388111114501953s
Interlinking | sameAs chians check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1125936508178711s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11358880996704102s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1123652458190918s
Timeliness | dataset update frequency check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11379504203796387s
Currency | Creation date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.22640538215637207s
Currency | Modification date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.22885346412658691s
Rep.Conc. | URIs length for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.227862119674683s
Interoperability | New vocabularies check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11429548263549805s
Accuracy | Check Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11122775077819824s
Accuracy | Check Inverse Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11269164085388184s
Accuracy | Check Empty annotation labels for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.470386505126953s
Accuracy | Check White space in annotation for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24505209922790527s
Accuracy | Check Datatype consistency for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.551431655883789s
Consistency | Disjoint class check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11436080932617188s
Consistency | Check Misplaced properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.0749142169952393s
Consistency | Check Ontology hijacking for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.913539886474609s
Consistency | Check Invalid usage of undefined classes for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2241928577423096s
Consistency | Check Invalid usage of undefined properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.2614259719848633s
Conciseness | Check Extensional conciseness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.6738035678863525s
Security | Sign check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11270451545715332s
Availability | Check URIs Dereferenciability for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3442.1851212978363s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.5422029495239258s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.02103447914123535s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.193450927734375e-05s
Interoperability | Check the re-using of existing vocabs for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.0531158447265625e-06s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.1920928955078125e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 3547.2278892993927s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.17185163497924805s
Availability | VoID file availability check for business.data.gov.uk took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.2629413604736328s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.021747350692749023s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.340576171875e-05s
Believability | Calculation of trust value for business.data.gov.uk took 9.059906005859375e-06s
INFO | --- Analysis for business-data-gov-uk took 2.67169189453125s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.4494454860687256s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0005230903625488281s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 1.8854806423187256s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.7695949077606201s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.373157262802124s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.6443955898284912s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 44.97131824493408s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.28090977668762207s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.16324996948242188s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.3360311985015869s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.2871830463409424s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.2847330570220947s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.3175361156463623s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 19.79164958000183s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.3156132698059082s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.3122706413269043s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.5437228679656982s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.2862565517425537s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.28382229804992676s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.2722463607788086s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 10.935989618301392s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.43865966796875e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.28540515899658203s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.35607481002807617s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.27464818954467773s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.276700496673584s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.2755248546600342s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.5462257862091064s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.569998025894165s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 2.8776443004608154s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.27797746658325195s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4304349422454834s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.44886207580566406s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 0.9572312831878662s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03358054161071777s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.0284273624420166s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.3152923583984375s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.375108003616333s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.3620116710662842s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.125149965286255s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.299586534500122s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.4160892963409424s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.032129526138305664s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.27889275550842285s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.28282856941223145s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1411.301968574524s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.33591556549072266s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.021689414978027344s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 6.67572021484375e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.14984130859375e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.1920928955078125e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.3113021850585938e-05s
INFO | --- Analysis for BVMC took 1539.2333102226257s
Availability | SPARQL endpoint availability check for cablegate took 1.457214117050171s
Availability | VoID file availability check for cablegate took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for cablegate took 0.271756649017334s
Reputation | Calculation of the PageRank for cablegate took 0.020865678787231445s
Interlinking | Calculation of Degree of Connection for cablegate took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.723403930664062e-05s
Believability | Calculation of trust value for cablegate took 1.1205673217773438e-05s
INFO | --- Analysis for cablegate took 16.11269998550415s
Availability | SPARQL endpoint availability check for Calames took 4.363059997558594e-05s
Availability | VoID file availability check for Calames took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for Calames took 0.2642970085144043s
Reputation | Calculation of the PageRank for Calames took 0.02278590202331543s
Interlinking | Calculation of Degree of Connection for Calames took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Calames took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Calames took 3.886222839355469e-05s
Believability | Calculation of trust value for Calames took 1.0967254638671875e-05s
INFO | --- Analysis for calames took 3.876415491104126s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.47277069091796875s
Availability | VoID file availability check for CaLiGraph took 0.0005178451538085938s
Extra | Recovery of all triples for CaLiGraph took 1.539480447769165s
Performance | Total latancy measurement for CaLiGraph took 0.9352877140045166s
Amount of data | Number of triples check for CaLiGraph took 13.687357425689697s
Interoperability | New terms check for CaLiGraph took 1.8689286708831787s
Versatility | Languages check for CaLiGraph took 60.262189865112305s
Interpretability | Number of blank nodes check for CaLiGraph took 0.21028733253479004s
Security | Check HTTPS for CaLiGraph took 0.11171865463256836s
Interpretability | RDF structures check for CaLiGraph took 0.2617959976196289s
Versatility | Serialization formats check for CaLiGraph took 0.2910730838775635s
Availability | RDF dump link check for CaLiGraph took 0.22921061515808105s
License | MR license check for CaLiGraph took 0.37563419342041016s
License | HR license check for CaLiGraph took 60.26495385169983s
Amount of data | Number of property check for CaLiGraph took 0.21898698806762695s
Understandability | Number of label check for CaLiGraph took 4.04482889175415s
Understandability | URI regex check for CaLiGraph took 0.5373222827911377s
Understandability | Vocabs check for CaLiGraph took 0.2768256664276123s
Verifiability | Authors check for CaLiGraph took 0.27565670013427734s
Verifiability | Publishers check for CaLiGraph took 0.20943498611450195s
Performance | Throughput check for CaLiGraph took 10.928574800491333s
Amount of data | Check the number of entities for CaLiGraph took 0.012658834457397461s
Verifiability | Contribs. check for CaLiGraph took 0.22607016563415527s
Interlinking | sameAs chians check for CaLiGraph took 0.6865749359130859s
Interlinking | skos check for CaLiGraph took 0.40728759765625s
Interlinking | skos check for CaLiGraph took 0.1846771240234375s
Timeliness | dataset update frequency check for CaLiGraph took 0.2955620288848877s
Currency | Creation date check for CaLiGraph took 0.46258068084716797s
Currency | Modification date check for CaLiGraph took 0.421245813369751s
Rep.Conc. | URIs length for CaLiGraph took 61.05011177062988s
Interoperability | New vocabularies check for CaLiGraph took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.20821118354797363s
Accuracy | Check Functional Property for CaLiGraph took 0.2620365619659424s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2545762062072754s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5285563468933105s
Accuracy | Check White space in annotation for CaLiGraph took 0.025772809982299805s
Accuracy | Check Datatype consistency for CaLiGraph took 0.04948544502258301s
Consistency | Disjoint class check for CaLiGraph took 0.2107551097869873s
Consistency | Check Misplaced properties for CaLiGraph took 60.724748849868774s
Consistency | Misplaced classes for CaLiGraph took 0.42149949073791504s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9062914848327637s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.3011202812194824s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.5374550819397s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03345680236816406s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.3845367431640625s
Security | Sign check for CaLiGraph took 0.4101121425628662s
Availability | Check URIs Dereferenciability for CaLiGraph took 9.969057321548462s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.3993511199951172s
Reputation | Calculation of the PageRank for CaLiGraph took 0.022887229919433594s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.457069396972656e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.6689300537109375e-06s
Believability | Calculation of trust value for CaLiGraph took 1.2159347534179688e-05s
INFO | --- Analysis for CaLiGraph took 1429.6896362304688s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.20731091499328613s
Availability | VoID file availability check for CaLiGraph took 0.0007288455963134766s
Extra | Recovery of all triples for CaLiGraph took 1.4602792263031006s
Performance | Total latancy measurement for CaLiGraph took 0.9356229305267334s
Amount of data | Number of triples check for CaLiGraph took 13.632039785385132s
Interoperability | New terms check for CaLiGraph took 1.8658084869384766s
Versatility | Languages check for CaLiGraph took 60.255969285964966s
Interpretability | Number of blank nodes check for CaLiGraph took 0.20814156532287598s
Security | Check HTTPS for CaLiGraph took 0.11126112937927246s
Interpretability | RDF structures check for CaLiGraph took 0.22791790962219238s
Versatility | Serialization formats check for CaLiGraph took 0.23719477653503418s
Availability | RDF dump link check for CaLiGraph took 0.20670080184936523s
License | MR license check for CaLiGraph took 0.2474353313446045s
License | HR license check for CaLiGraph took 60.265724420547485s
Amount of data | Number of property check for CaLiGraph took 0.21475720405578613s
Understandability | Number of label check for CaLiGraph took 3.2456438541412354s
Understandability | URI regex check for CaLiGraph took 0.41280603408813477s
Understandability | Vocabs check for CaLiGraph took 0.21431732177734375s
Verifiability | Authors check for CaLiGraph took 0.21514153480529785s
Verifiability | Publishers check for CaLiGraph took 0.208251953125s
Performance | Throughput check for CaLiGraph took 10.889283418655396s
Amount of data | Check the number of entities for CaLiGraph took 0.01373600959777832s
Verifiability | Contribs. check for CaLiGraph took 0.2094407081604004s
Interlinking | sameAs chians check for CaLiGraph took 0.615098237991333s
Interlinking | skos check for CaLiGraph took 0.21643590927124023s
Interlinking | skos check for CaLiGraph took 0.1840534210205078s
Timeliness | dataset update frequency check for CaLiGraph took 0.214371919631958s
Currency | Creation date check for CaLiGraph took 0.42173051834106445s
Currency | Modification date check for CaLiGraph took 0.4210624694824219s
Rep.Conc. | URIs length for CaLiGraph took 60.86752700805664s
Interoperability | New vocabularies check for CaLiGraph took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.20870471000671387s
Accuracy | Check Functional Property for CaLiGraph took 0.21075773239135742s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.20436453819274902s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.48824501037597656s
Accuracy | Check White space in annotation for CaLiGraph took 0.026095151901245117s
Accuracy | Check Datatype consistency for CaLiGraph took 0.04816794395446777s
Consistency | Disjoint class check for CaLiGraph took 0.20978379249572754s
Consistency | Check Misplaced properties for CaLiGraph took 60.753913164138794s
Consistency | Misplaced classes for CaLiGraph took 0.4171130657196045s
Consistency | Check Ontology hijacking for CaLiGraph took 1.8505706787109375s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2490108013153076s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.492090463638306s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.029392719268798828s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4718611240386963s
Security | Sign check for CaLiGraph took 0.26740336418151855s
Availability | Check URIs Dereferenciability for CaLiGraph took 15.056588172912598s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.3439371585845947s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02082037925720215s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.772445678710938e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.1920928955078125e-06s
Believability | Calculation of trust value for CaLiGraph took 1.1920928955078125e-05s
INFO | --- Analysis for caligraph took 1830.482980966568s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.05355477333068848s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.2703588008880615s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.021080493927001953s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.409385681152344e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.239776611328125e-05s
INFO | --- Analysis for cap-italy-rdf took 2.579662322998047s
Availability | SPARQL endpoint availability check for person took 9.036064147949219e-05s
Availability | VoID file availability check for person took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for person took 0.26174497604370117s
Reputation | Calculation of the PageRank for person took 0.020803213119506836s
Interlinking | Calculation of Degree of Connection for person took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for person took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for person took 3.337860107421875e-05s
Believability | Calculation of trust value for person took 1.2636184692382812e-05s
INFO | --- Analysis for card took 2.4214799404144287s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.57763671875e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0008063316345214844s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.27483439445495605s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.021695613861083984s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0010242462158203125s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 5.6743621826171875e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.2159347534179688e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 3.0879740715026855s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.8527543544769287s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.2620851993560791s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.0209500789642334s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 3.743171691894531e-05s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 1.0967254638671875e-05s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 3.8239247798919678s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.202957153320312e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.26420044898986816s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.021106719970703125s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010347366333007812s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.1920928955078125e-05s
INFO | --- Analysis for ce4r took 28.42795968055725s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.430757999420166s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005192756652832031s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.017103672027588s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.743553638458252s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3735814094543457s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6830947399139404s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.133819341659546s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17930388450622559s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.27759313583374023s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16870903968811035s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1494002342224121s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.314755916595459s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.36612534523010254s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.22584080696105957s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.48235440254211426s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2966325283050537s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1476283073425293s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19968819618225098s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20657730102539062s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.597214221954346s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.224082946777344e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2767951488494873s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14445257186889648s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7241976261138916s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14861536026000977s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16911101341247559s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.8394567966461182s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6070609092712402s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.2119553089141846s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15170526504516602s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.5675489902496338s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028712034225463867s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.02791571617126465s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.39252758026123047s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.30802321434021s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.9532954692840576s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.298966407775879s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.5093553066253662s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.031098604202270508s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.20550799369812012s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15657877922058105s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2891.7304797172546s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.45499444007873535s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.02049994468688965s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0006816387176513672s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.9073486328125e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 6.67572021484375e-06s
INFO | --- Analysis for ceo took 3016.209380865097s
Availability | SPARQL endpoint availability check for Chat Game corpus took 8.988380432128906e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.27764344215393066s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.02142500877380371s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.814697265625e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.1682510375976562e-05s
INFO | --- Analysis for chat-game-corpus took 12.542996168136597s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 9.1552734375e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0009024143218994141s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.26671648025512695s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.021458148956298828s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 6.556510925292969e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.0013580322265625e-05s
INFO | --- Analysis for chem2bio2rdf took 134.2912471294403s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.5003268718719482s
Availability | VoID file availability check for ChEMBL RDF took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.26342058181762695s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.02119731903076172s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.935264587402344e-05s
Believability | Calculation of trust value for ChEMBL RDF took 9.775161743164062e-06s
INFO | --- Analysis for chembl-rdf took 3.505876064300537s
Availability | SPARQL endpoint availability check for chemdb  dataset took 0.7739367485046387s
Availability | VoID file availability check for chemdb  dataset took 0.00047898292541503906s
Extra | Recovery of all triples for chemdb  dataset took 4.93779993057251s
Performance | Total latancy measurement for chemdb  dataset took 2.4783318042755127s
Amount of data | Number of triples check for chemdb  dataset took 0.5452449321746826s
Interoperability | New terms check for chemdb  dataset took 3.4473395347595215s
Versatility | Languages check for chemdb  dataset took 33.47273540496826s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5063807964324951s
Interpretability | RDF structures check for chemdb  dataset took 2.6865317821502686s
Versatility | Serialization formats check for chemdb  dataset took 1.5660207271575928s
Availability | RDF dump link check for chemdb  dataset took 0.6180012226104736s
License | MR license check for chemdb  dataset took 2.781243085861206s
License | HR license check for chemdb  dataset took 4.298808336257935s
Amount of data | Number of property check for chemdb  dataset took 0.515695333480835s
Understandability | Number of label check for chemdb  dataset took 5.345344305038452s
Understandability | URI regex check for chemdb  dataset took 1.836059331893921s
Understandability | Vocabs check for chemdb  dataset took 0.8164610862731934s
Verifiability | Authors check for chemdb  dataset took 1.1351721286773682s
Verifiability | Publishers check for chemdb  dataset took 0.8069710731506348s
Performance | Throughput check for chemdb  dataset took 14.614702939987183s
Amount of data | Check the number of entities for chemdb  dataset took 6.866455078125e-05s
Verifiability | Contribs. check for chemdb  dataset took 1.0340559482574463s
Interlinking | sameAs chians check for chemdb  dataset took 1.546161413192749s
Interlinking | skos check for chemdb  dataset took 2.2248826026916504s
Interlinking | skos check for chemdb  dataset took 0.4844369888305664s
Timeliness | dataset update frequency check for chemdb  dataset took 1.0776538848876953s
Currency | Creation date check for chemdb  dataset took 1.5434367656707764s
Currency | Modification date check for chemdb  dataset took 1.0074191093444824s
Rep.Conc. | URIs length for chemdb  dataset took 2.9178316593170166s
Interoperability | New vocabularies check for chemdb  dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5027847290039062s
Accuracy | Check Functional Property for chemdb  dataset took 0.5584549903869629s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.5344691276550293s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.296968936920166s
Accuracy | Check White space in annotation for chemdb  dataset took 0.0299532413482666s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.035257816314697266s
Consistency | Disjoint class check for chemdb  dataset took 0.9732725620269775s
Consistency | Check Misplaced properties for chemdb  dataset took 1.1975493431091309s
Consistency | Misplaced classes for chemdb  dataset took 0.5997562408447266s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.4490909576416016s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.3178119659423828s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 2.0019006729125977s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.03236865997314453s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5086240768432617s
Security | Sign check for chemdb  dataset took 2.3246912956237793s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2642.1962826251984s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.5499522686004639s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.02128887176513672s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 6.914138793945312e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb  dataset took 1.0251998901367188e-05s
INFO | --- Analysis for chemdb-basicInfo took 4795.960201025009s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5166771411895752s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0005767345428466797s
Extra | Recovery of all triples for chemdb estimated properties dataset took 13.187367677688599s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.4637200832366943s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.533536434173584s
Interoperability | New terms check for chemdb estimated properties dataset took 3.8247337341308594s
Versatility | Languages check for chemdb estimated properties dataset took 30.896779775619507s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5077941417694092s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5206468105316162s
Versatility | Serialization formats check for chemdb estimated properties dataset took 1.400385856628418s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.8147909641265869s
License | MR license check for chemdb estimated properties dataset took 2.6829371452331543s
License | HR license check for chemdb estimated properties dataset took 3.9295356273651123s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5111773014068604s
Understandability | Number of label check for chemdb estimated properties dataset took 5.045318603515625s
Understandability | URI regex check for chemdb estimated properties dataset took 1.8612852096557617s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.8199853897094727s
Verifiability | Authors check for chemdb estimated properties dataset took 1.0266854763031006s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.8051927089691162s
Performance | Throughput check for chemdb estimated properties dataset took 14.121831893920898s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 0.000102996826171875s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.813410758972168s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 1.1606028079986572s
Interlinking | skos check for chemdb estimated properties dataset took 2.0515856742858887s
Interlinking | skos check for chemdb estimated properties dataset took 0.4831981658935547s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 1.1457045078277588s
Currency | Creation date check for chemdb estimated properties dataset took 1.3559443950653076s
Currency | Modification date check for chemdb estimated properties dataset took 0.9987165927886963s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 3.3404898643493652s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.4817216396331787s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.7689414024353027s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.7636010646820068s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 3.347918748855591s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.02932429313659668s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03282642364501953s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.8119349479675293s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.2064406871795654s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.6018993854522705s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 3.8318822383880615s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.2543354034423828s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 1.9502227306365967s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03152966499328613s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.5198080539703369s
Security | Sign check for chemdb estimated properties dataset took 2.031930446624756s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2613.7670452594757s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.5707857608795166s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.021251201629638672s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 5.245208740234375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.1205673217773438e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 4784.684265375137s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5171782970428467s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0004975795745849609s
Extra | Recovery of all triples for chemdb phase transition dataset took 9.08124041557312s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.4509854316711426s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5341756343841553s
Interoperability | New terms check for chemdb phase transition dataset took 3.62459659576416s
Versatility | Languages check for chemdb phase transition dataset took 29.068636178970337s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.509056806564331s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5114109516143799s
Versatility | Serialization formats check for chemdb phase transition dataset took 1.406989336013794s
Availability | RDF dump link check for chemdb phase transition dataset took 0.7908143997192383s
License | MR license check for chemdb phase transition dataset took 2.8646085262298584s
License | HR license check for chemdb phase transition dataset took 3.838820219039917s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5202102661132812s
Understandability | Number of label check for chemdb phase transition dataset took 4.969431638717651s
Understandability | URI regex check for chemdb phase transition dataset took 1.8793814182281494s
Understandability | Vocabs check for chemdb phase transition dataset took 0.779482364654541s
Verifiability | Authors check for chemdb phase transition dataset took 0.96805739402771s
Verifiability | Publishers check for chemdb phase transition dataset took 0.7873554229736328s
Performance | Throughput check for chemdb phase transition dataset took 14.606112480163574s
Amount of data | Check the number of entities for chemdb phase transition dataset took 7.05718994140625e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.8055679798126221s
Interlinking | sameAs chians check for chemdb phase transition dataset took 1.1475880146026611s
Interlinking | skos check for chemdb phase transition dataset took 2.2892704010009766s
Interlinking | skos check for chemdb phase transition dataset took 0.4824037551879883s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 1.0900850296020508s
Currency | Creation date check for chemdb phase transition dataset took 1.3090932369232178s
Currency | Modification date check for chemdb phase transition dataset took 1.0075290203094482s
Rep.Conc. | URIs length for chemdb phase transition dataset took 3.117978572845459s
Interoperability | New vocabularies check for chemdb phase transition dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.4852473735809326s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.808114767074585s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.7888243198394775s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 3.02959942817688s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.03030109405517578s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03282046318054199s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.6019151210784912s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2049527168273926s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.5987780094146729s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 3.8609535694122314s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.2563982009887695s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 1.9506773948669434s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.03191852569580078s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5126712322235107s
Security | Sign check for chemdb phase transition dataset took 1.8898241519927979s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2673.820718765259s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.6922116279602051s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.021539688110351562s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 8.177757263183594e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.1205673217773438e-05s
INFO | --- Analysis for chemdb-phaseTransition took 4884.789769649506s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5226645469665527s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0005064010620117188s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 13.261932373046875s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.4535582065582275s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.531590461730957s
Interoperability | New terms check for chemdb thermochemistry dataset took 4.389646768569946s
Versatility | Languages check for chemdb thermochemistry dataset took 30.584246158599854s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.517988920211792s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5139591693878174s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 1.4048988819122314s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.8251466751098633s
License | MR license check for chemdb thermochemistry dataset took 2.9009220600128174s
License | HR license check for chemdb thermochemistry dataset took 3.9990227222442627s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5180842876434326s
Understandability | Number of label check for chemdb thermochemistry dataset took 5.000402927398682s
Understandability | URI regex check for chemdb thermochemistry dataset took 1.8094704151153564s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.8123464584350586s
Verifiability | Authors check for chemdb thermochemistry dataset took 1.1436316967010498s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.7866897583007812s
Performance | Throughput check for chemdb thermochemistry dataset took 15.147329568862915s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 6.198883056640625e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 1.7893147468566895s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 1.0523724555969238s
Interlinking | skos check for chemdb thermochemistry dataset took 1.8548851013183594s
Interlinking | skos check for chemdb thermochemistry dataset took 0.481522798538208s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 1.115499496459961s
Currency | Creation date check for chemdb thermochemistry dataset took 1.2850663661956787s
Currency | Modification date check for chemdb thermochemistry dataset took 1.0064210891723633s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.3608243465423584s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.49177980422973633s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.7746443748474121s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.7500550746917725s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 3.046693801879883s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.029921293258666992s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.0331110954284668s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.7857105731964111s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2102997303009033s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.5924365520477295s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 3.88961124420166s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.2507030963897705s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 1.981619119644165s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.03348541259765625s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5100269317626953s
Security | Sign check for chemdb thermochemistry dataset took 1.9452829360961914s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2646.384169101715s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.6184346675872803s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.020891427993774414s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.67572021484375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 1.0728836059570312e-05s
INFO | --- Analysis for chemdb-thermochemistry took 4877.304648637772s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.315376281738281e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0007688999176025391s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.2768411636352539s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.021401405334472656s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.337860107421875e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.0728836059570312e-05s
INFO | --- Analysis for chempedia-rdf took 8.978646039962769s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.2438507080078125e-05s
Availability | VoID file availability check for Chiman Maru took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.2637166976928711s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020708322525024414s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.1948089599609375e-05s
Believability | Calculation of trust value for Chiman Maru took 1.049041748046875e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 2.438467264175415s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.8945777416229s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.31835079193115234s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.02150416374206543s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 4.363059997558594e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 797.9309067726135s
Availability | SPARQL endpoint availability check for Chronicling America took 8.7738037109375e-05s
Availability | VoID file availability check for Chronicling America took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.273958683013916s
Reputation | Calculation of the PageRank for Chronicling America took 0.020782947540283203s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 9.72747802734375e-05s
Believability | Calculation of trust value for Chronicling America took 5.984306335449219e-05s
INFO | --- Analysis for chronicling-america took 5.879402160644531s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.538379430770874s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006768703460693359s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 75.85734367370605s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.3568973541259766s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.7208216190338135s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.3028616905212402s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.6948230266571045s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.6521186828613281s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3655531406402588s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.2610292434692383s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 8.847196102142334s
License | MR license check for Cultural Heritage Thesaurus took 0.2669961452484131s
License | HR license check for Cultural Heritage Thesaurus took 0.4236011505126953s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.2602558135986328s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.31290602684020996s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5168836116790771s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.30187153816223145s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.263019323348999s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.3026142120361328s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.008549690246582s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 7.152557373046875e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.2653543949127197s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.26714348793029785s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.29767298698425293s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.28876495361328125s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.26286792755126953s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.5408873558044434s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.5457251071929932s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 27.6419939994812s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 1.1162137985229492s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.2626957893371582s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.2771131992340088s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.2631564140319824s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 6.34429931640625s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.21903014183044434s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.27429723739624023s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.2311604022979736s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.2883791923522949s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.529460668563843s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.109281539916992s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.000152587890625s
Security | Sign check for Cultural Heritage Thesaurus took 0.28587865829467773s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 303.4317581653595s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.3393895626068115s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.042954444885253906s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00010085105895996094s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 2.407175302505493s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for cht took 484.3276219367981s
Availability | SPARQL endpoint availability check for ciard-ring took 8.535385131835938e-05s
Availability | VoID file availability check for ciard-ring took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.27783942222595215s
Reputation | Calculation of the PageRank for ciard-ring took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.2438507080078125e-05s
Believability | Calculation of trust value for ciard-ring took 1.0967254638671875e-05s
INFO | --- Analysis for ciard-ring took 4.585084438323975s
Availability | SPARQL endpoint availability check for Cine Figure took 8.487701416015625e-05s
Availability | VoID file availability check for Cine Figure took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.266355037689209s
Reputation | Calculation of the PageRank for Cine Figure took 0.021102190017700195s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.673004150390625e-05s
Believability | Calculation of trust value for Cine Figure took 1.1682510375976562e-05s
INFO | --- Analysis for Cine_Figure took 2.473173141479492s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 2.5711677074432373s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.000782012939453125s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.26698994636535645s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.021001100540161133s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0009205341339111328s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 5.030632019042969e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.1920928955078125e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 17.76521921157837s
Availability | SPARQL endpoint availability check for CIPFA took 0.00013375282287597656s
Availability | VoID file availability check for CIPFA took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for CIPFA took 0.27466320991516113s
Reputation | Calculation of the PageRank for CIPFA took 0.020817279815673828s
Interlinking | Calculation of Degree of Connection for CIPFA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CIPFA took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.361701965332031e-05s
Believability | Calculation of trust value for CIPFA took 1.1920928955078125e-05s
INFO | --- Analysis for cipfa took 2.6066009998321533s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 1.0141286849975586s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.27324604988098145s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020911216735839844s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00039267539978027344s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.1444091796875e-05s
INFO | --- Analysis for ckan took 6.6877405643463135s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.5678167343139648s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.2871413230895996s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.021023035049438477s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for CLaSSES took 4.104469299316406s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 8.559226989746094e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0007498264312744141s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.26755833625793457s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.02254176139831543s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.266334533691406e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.1682510375976562e-05s
INFO | --- Analysis for classical_temples took 4.35973048210144s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 0.9032444953918457s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.27977895736694336s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020750045776367188s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.034706115722656e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 9.298324584960938e-06s
INFO | --- Analysis for clean-energy-data-reegle took 5.013962507247925s
Availability | SPARQL endpoint availability check for CLLD-afbo took 8.797645568847656e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.2770090103149414s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020921945571899414s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.367134094238281e-05s
Believability | Calculation of trust value for CLLD-afbo took 1.1920928955078125e-05s
INFO | --- Analysis for clld-afbo took 3.440913200378418s
Availability | SPARQL endpoint availability check for CLLD-APICS took 8.606910705566406e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.2635364532470703s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.021327495574951172s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0008096694946289062s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 8.344650268554688e-05s
Believability | Calculation of trust value for CLLD-APICS took 1.1205673217773438e-05s
INFO | --- Analysis for clld-apics took 3.4897286891937256s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 9.274482727050781e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.28044557571411133s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.02069568634033203s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.6716461181640625e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 1.0967254638671875e-05s
INFO | --- Analysis for clld-ewave took 3.3968119621276855s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 8.821487426757812e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.27618956565856934s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.02103734016418457s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.560585021972656e-05s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.3113021850585938e-05s
INFO | --- Analysis for clld-glottolog took 3.4091427326202393s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.1961669921875e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.266221284866333s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.02097487449645996s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 7.700920104980469e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.0967254638671875e-05s
INFO | --- Analysis for clld-phoible took 3.372305154800415s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 8.487701416015625e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.27274060249328613s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.02088642120361328s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.677078247070312e-05s
Believability | Calculation of trust value for CLLD-SAILS took 1.33514404296875e-05s
INFO | --- Analysis for clld-sails took 3.4582927227020264s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.3392181396484375e-05s
Availability | VoID file availability check for CLLD-WALS took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.2624788284301758s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.02215862274169922s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.249282836914062e-05s
Believability | Calculation of trust value for CLLD-WALS took 1.2874603271484375e-05s
INFO | --- Analysis for clld-wals took 3.464759111404419s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 0.00010585784912109375s
Availability | VoID file availability check for CLLD-WOLD took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.26656365394592285s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.510185241699219e-05s
Believability | Calculation of trust value for CLLD-WOLD took 1.1682510375976562e-05s
INFO | --- Analysis for clld-wold took 3.4463717937469482s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.10648012161254883s
Availability | VoID file availability check for Cooperation Databank took 0.0004031658172607422s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.26621413230895996s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.021126985549926758s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.62396240234375e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.1205673217773438e-05s
INFO | --- Analysis for CoDa took 2.578766107559204s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.7574241161346436s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.26057910919189453s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.021054744720458984s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.409385681152344e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 9.059906005859375e-06s
INFO | --- Analysis for coins-openuplabs took 3.248598337173462s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 2.9004456996917725s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.27005553245544434s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.020746231079101562s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.034706115722656e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 6.9141387939453125e-06s
INFO | --- Analysis for CoLChina_sp2000 took 6.7436628341674805s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.06497454643249512s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.00021338462829589844s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.2666635513305664s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020786046981811523s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.933906555175781e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for colinda took 2.591334342956543s
Availability | SPARQL endpoint availability check for CN  2012 took 25.428277015686035s
Availability | VoID file availability check for CN  2012 took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.28919196128845215s
Reputation | Calculation of the PageRank for CN  2012 took 0.0210878849029541s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.2438507080078125e-05s
Believability | Calculation of trust value for CN  2012 took 4.5299530029296875e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 124.42809820175171s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.44172096252441406s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.2714200019836426s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.022490739822387695s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for CompHistSem took 4.063587427139282s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 1.2274055480957031s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.27135324478149414s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.021079540252685547s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 4.00543212890625e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 9.059906005859375e-06s
INFO | --- Analysis for comsode-d3-2 took 6.513758897781372s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 0.00013113021850585938s
Availability | VoID file availability check for 2011 US Congress People took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.26279306411743164s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.0217287540435791s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.7738037109375e-05s
Believability | Calculation of trust value for 2011 US Congress People took 1.1444091796875e-05s
INFO | --- Analysis for congresspeople took 3.5037896633148193s
Availability | SPARQL endpoint availability check for MIMO took 0.34694409370422363s
Availability | VoID file availability check for MIMO took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for MIMO took 0.27126049995422363s
Reputation | Calculation of the PageRank for MIMO took 0.021975040435791016s
Interlinking | Calculation of Degree of Connection for MIMO took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.33514404296875e-05s
Believability | Calculation of trust value for MIMO took 1.049041748046875e-05s
INFO | --- Analysis for CONNECTED took 3.9170963764190674s
Availability | SPARQL endpoint availability check for Copyright Free Music took 8.893013000488281e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.2654132843017578s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020738601684570312s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.314018249511719e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.1444091796875e-05s
INFO | --- Analysis for Copyright_Free_Music took 3.1837198734283447s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.220008850097656e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.2756211757659912s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.021836042404174805s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.82012939453125e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.3828277587890625e-05s
INFO | --- Analysis for copyrighttermbank took 37.449864625930786s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.2710583209991455s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0007317066192626953s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.27582550048828125s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.022814512252807617s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 4.00543212890625e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.0728836059570312e-05s
INFO | --- Analysis for core took 7.60337495803833s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.5046396255493164s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.00047779083251953125s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 126.01084113121033s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.9009230136871338s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 29.467458486557007s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.205107927322388s
Versatility | Languages check for Corine linked dataset @PSNC took 300.24146604537964s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 2.4870762825012207s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.3606081008911133s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 8.990231037139893s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.20717072486877441s
License | MR license check for Corine linked dataset @PSNC took 0.9736642837524414s
License | HR license check for Corine linked dataset @PSNC took 300.2378759384155s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.18090581893920898s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.830030918121338s
Understandability | URI regex check for Corine linked dataset @PSNC took 0.48175859451293945s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.24113059043884277s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.3751487731933594s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.5876786708831787s
Performance | Throughput check for Corine linked dataset @PSNC took 10.737090587615967s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 0.00010967254638671875s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.21186089515686035s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.23913145065307617s
Interlinking | skos check for Corine linked dataset @PSNC took 1.1036193370819092s
Interlinking | skos check for Corine linked dataset @PSNC took 0.39336347579956055s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 5.390361785888672s
Currency | Creation date check for Corine linked dataset @PSNC took 2.0720601081848145s
Currency | Modification date check for Corine linked dataset @PSNC took 0.537968635559082s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 152.65828800201416s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.1811072826385498s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.22156262397766113s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.22601675987243652s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 39.7241268157959s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.626859426498413s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.6142776012420654s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.2883458137512207s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 86.25567555427551s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.268797159194946s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 38.10343551635742s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.3312833309173584s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 86.7993712425232s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.6792259216308594s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.523944616317749s
Security | Sign check for Corine linked dataset @PSNC took 0.5515139102935791s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 9.88311219215393s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.4395911693572998s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.021487712860107422s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.266334533691406e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.0728836059570312e-05s
INFO | --- Analysis for Corine_linked_dataset took 2284.3085663318634s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 8.821487426757812e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.27530455589294434s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020545244216918945s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.7220458984375e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.0251998901367188e-05s
INFO | --- Analysis for cornetto took 12.566279888153076s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.14028644561767578s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005686283111572266s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 197.68363404273987s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.5911657810211182s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 71.47900581359863s
Interoperability | New terms check for Corporate Body Named Authority List  took 62.4660439491272s
Versatility | Languages check for Corporate Body Named Authority List  took 300.1146399974823s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 72.64960432052612s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.327526330947876s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.52557373046875s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 3.975297451019287s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.1562671661376953s
License | MR license check for Corporate Body Named Authority List  took 0.49108171463012695s
License | HR license check for Corporate Body Named Authority List  took 300.1047360897064s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.1503150463104248s
Understandability | Number of label check for Corporate Body Named Authority List  took 2.1071410179138184s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.42962026596069336s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.10220694541931152s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.22174477577209473s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.16396427154541016s
Performance | Throughput check for Corporate Body Named Authority List  took 10.478104591369629s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 7.176399230957031e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.2056431770324707s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 7.0381691455841064s
Interlinking | skos check for Corporate Body Named Authority List  took 0.39401721954345703s
Interlinking | skos check for Corporate Body Named Authority List  took 0.1432490348815918s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.35477304458618164s
Currency | Creation date check for Corporate Body Named Authority List  took 0.4172513484954834s
Currency | Modification date check for Corporate Body Named Authority List  took 0.16692280769348145s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 433.0992977619171s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.15623092651367188s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.1853618621826172s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.15925312042236328s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 39.308971643447876s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.0717272758483887s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.6078104972839355s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.17030906677246094s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.44719552993774s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.288447141647339s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 41.15717387199402s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.6413681507110596s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.3565046787262s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 2.958401918411255s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.3639519214630127s
Security | Sign check for Corporate Body Named Authority List  took 0.12674951553344727s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 10.91132664680481s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.7820224761962891s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.02137899398803711s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.1920928955078125e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.0728836059570312e-05s
INFO | --- Analysis for corporate-body took 14292.583453893661s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.5610301494598389s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.27335619926452637s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.021929025650024414s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.4781951904296875e-05s
INFO | --- Analysis for CorpusFibonacci took 3.9912338256835938s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.12723684310913086s
Availability | VoID file availability check for Country Name Authority List took 0.001093149185180664s
Extra | Recovery of all triples for Country Name Authority List took 205.32374048233032s
Performance | Total latancy measurement for Country Name Authority List took 0.5731766223907471s
Amount of data | Number of triples check for Country Name Authority List took 85.22629714012146s
Interoperability | New terms check for Country Name Authority List took 62.48911905288696s
Versatility | Languages check for Country Name Authority List took 300.1293783187866s
Interpretability | Number of blank nodes check for Country Name Authority List took 16.99202585220337s
Security | Check HTTPS for Country Name Authority List took 0.3022456169128418s
Interpretability | RDF structures check for Country Name Authority List took 0.3141968250274658s
Versatility | Serialization formats check for Country Name Authority List took 3.8106014728546143s
Availability | RDF dump link check for Country Name Authority List took 0.160353422164917s
License | MR license check for Country Name Authority List took 0.5573246479034424s
License | HR license check for Country Name Authority List took 300.1011416912079s
Amount of data | Number of property check for Country Name Authority List took 0.14229869842529297s
Understandability | Number of label check for Country Name Authority List took 1.6051299571990967s
Understandability | URI regex check for Country Name Authority List took 0.4603128433227539s
Understandability | Vocabs check for Country Name Authority List took 0.10384988784790039s
Verifiability | Authors check for Country Name Authority List took 0.2757282257080078s
Verifiability | Publishers check for Country Name Authority List took 0.21198487281799316s
Performance | Throughput check for Country Name Authority List took 10.775998830795288s
Amount of data | Check the number of entities for Country Name Authority List took 7.43865966796875e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.09012079238891602s
Interlinking | sameAs chians check for Country Name Authority List took 8.156543493270874s
Interlinking | skos check for Country Name Authority List took 0.31377339363098145s
Interlinking | skos check for Country Name Authority List took 0.2885622978210449s
Timeliness | dataset update frequency check for Country Name Authority List took 0.27438974380493164s
Currency | Creation date check for Country Name Authority List took 0.4114186763763428s
Currency | Modification date check for Country Name Authority List took 0.1553795337677002s
Rep.Conc. | URIs length for Country Name Authority List took 437.4526274204254s
Interoperability | New vocabularies check for Country Name Authority List took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.15386009216308594s
Accuracy | Check Functional Property for Country Name Authority List took 0.1837320327758789s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.1456911563873291s
Accuracy | Check Empty annotation labels for Country Name Authority List took 39.03172063827515s
Accuracy | Check White space in annotation for Country Name Authority List took 3.0576987266540527s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.6061172485351562s
Consistency | Disjoint class check for Country Name Authority List took 0.15904688835144043s
Consistency | Check Misplaced properties for Country Name Authority List took 300.4190809726715s
Consistency | Misplaced classes for Country Name Authority List took 8.375593900680542s
Consistency | Check Ontology hijacking for Country Name Authority List took 43.12472414970398s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.705322027206421s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.446462392807s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.000093936920166s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.4188501834869385s
Security | Sign check for Country Name Authority List took 0.11152267456054688s
Availability | Check URIs Dereferenciability for Country Name Authority List took 14.766430139541626s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.6299810409545898s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.021276235580444336s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 5.507469177246094e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.430511474609375e-06s
Believability | Calculation of trust value for Country Name Authority List took 1.0967254638671875e-05s
INFO | --- Analysis for country-authority-list took 14144.395174980164s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.07032394409179688s
Availability | VoID file availability check for Courts thesaurus took 0.0002014636993408203s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.2682836055755615s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.021251201629638672s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.771087646484375e-05s
Believability | Calculation of trust value for Courts thesaurus took 9.298324584960938e-06s
INFO | --- Analysis for courts-thesaurus took 2.5499861240386963s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 20.364574909210205s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.26449155807495117s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.021146535873413086s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 7.987022399902344e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 9.5367431640625e-06s
INFO | --- Analysis for Covid-on-the-Web took 54.88593554496765s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.407973527908325s
Availability | VoID file availability check for CPA 2008 took 0.0007846355438232422s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.2709469795227051s
Reputation | Calculation of the PageRank for CPA 2008 took 0.02082371711730957s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.838539123535156e-05s
Believability | Calculation of trust value for CPA 2008 took 8.821487426757812e-06s
INFO | --- Analysis for cpa-2008 took 123.83549857139587s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.3688938617706299s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0005517005920410156s
Extra | Recovery of all triples for Cooperative Patent Classification took 28.75464391708374s
Performance | Total latancy measurement for Cooperative Patent Classification took 1.0354580879211426s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.29059624671936s
Versatility | Languages check for Cooperative Patent Classification took 100.19233989715576s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 100.29101133346558s
Interpretability | RDF structures check for Cooperative Patent Classification took 29.972130298614502s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.24270296096801758s
Availability | RDF dump link check for Cooperative Patent Classification took 0.2153468132019043s
License | MR license check for Cooperative Patent Classification took 0.22954607009887695s
License | HR license check for Cooperative Patent Classification took 90.30911874771118s
Amount of data | Number of property check for Cooperative Patent Classification took 0.21218466758728027s
Understandability | Number of label check for Cooperative Patent Classification took 90.3707389831543s
Understandability | URI regex check for Cooperative Patent Classification took 0.5243475437164307s
Understandability | Vocabs check for Cooperative Patent Classification took 0.20666146278381348s
Verifiability | Authors check for Cooperative Patent Classification took 0.2311556339263916s
Verifiability | Publishers check for Cooperative Patent Classification took 0.2629537582397461s
Performance | Throughput check for Cooperative Patent Classification took 10.652485370635986s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.343292236328125e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.21329975128173828s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.1727135181427002s
Interlinking | skos check for Cooperative Patent Classification took 0.19455671310424805s
Interlinking | skos check for Cooperative Patent Classification took 0.15793418884277344s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.15693354606628418s
Currency | Creation date check for Cooperative Patent Classification took 0.39029645919799805s
Currency | Modification date check for Cooperative Patent Classification took 0.38083744049072266s
Rep.Conc. | URIs length for Cooperative Patent Classification took 129.95387887954712s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 20.11339831352234s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 15.773613691329956s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.9185876846313477s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.826199769973755s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.27802038192749023s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 100.50013613700867s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 38.06309199333191s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.5619966983795166s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 101.64828729629517s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.768972396850586s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 16.014958381652832s
Security | Sign check for Cooperative Patent Classification took 0.3226025104522705s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 2.0250508785247803s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.4238729476928711s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.02196812629699707s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 1.9073486328125e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.0251998901367188e-05s
INFO | --- Analysis for CPC took 1278.8781192302704s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.344568967819214s
Availability | VoID file availability check for CPC 2008 took 0.0008149147033691406s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.2709639072418213s
Reputation | Calculation of the PageRank for CPC 2008 took 0.021428346633911133s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.839897155761719e-05s
Believability | Calculation of trust value for CPC 2008 took 8.344650268554688e-06s
INFO | --- Analysis for cpc-2008 took 124.55703806877136s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.765589952468872s
Availability | VoID file availability check for CPV  2003 took 0.0008211135864257812s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.3284916877746582s
Reputation | Calculation of the PageRank for CPV  2003 took 0.020943164825439453s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.504753112792969e-05s
Believability | Calculation of trust value for CPV  2003 took 8.58306884765625e-06s
INFO | --- Analysis for cpv-2003 took 114.04415798187256s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.509286880493164s
Availability | VoID file availability check for CPV 2008 took 0.0007898807525634766s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.26691508293151855s
Reputation | Calculation of the PageRank for CPV 2008 took 0.021071910858154297s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.482269287109375e-05s
Believability | Calculation of trust value for CPV 2008 took 1.0013580322265625e-05s
INFO | --- Analysis for cpv-2008 took 123.4324140548706s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 264.46988582611084s
Availability | VoID file availability check for crowdsourcing-fb took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.265042781829834s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020698070526123047s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.2438507080078125e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.0967254638671875e-05s
INFO | --- Analysis for crowdsourcing-fb took 537.5944511890411s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.449641466140747s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.26944994926452637s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.022645950317382812s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.982948303222656e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 7.152557373046875e-06s
INFO | --- Analysis for ctic-public-dataset took 8.928521633148193s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.41591548919677734s
Availability | VoID file availability check for CulturaLinkedData took 0.0006916522979736328s
Extra | Recovery of all triples for CulturaLinkedData took 132.08014583587646s
Performance | Total latancy measurement for CulturaLinkedData took 0.8122007846832275s
Amount of data | Number of triples check for CulturaLinkedData took 0.7450084686279297s
Interoperability | New terms check for CulturaLinkedData took 2.2067370414733887s
Versatility | Languages check for CulturaLinkedData took 60.38432717323303s
Interpretability | Number of blank nodes check for CulturaLinkedData took 0.1677565574645996s
Interpretability | RDF structures check for CulturaLinkedData took 0.4944424629211426s
Versatility | Serialization formats check for CulturaLinkedData took 0.5080037117004395s
Availability | RDF dump link check for CulturaLinkedData took 0.23955202102661133s
License | MR license check for CulturaLinkedData took 0.7299504280090332s
License | HR license check for CulturaLinkedData took 61.9263961315155s
Amount of data | Number of property check for CulturaLinkedData took 0.17536354064941406s
Understandability | Number of label check for CulturaLinkedData took 1.2700855731964111s
Understandability | URI regex check for CulturaLinkedData took 0.6062984466552734s
Understandability | Vocabs check for CulturaLinkedData took 0.2577519416809082s
Verifiability | Authors check for CulturaLinkedData took 0.31966638565063477s
Verifiability | Publishers check for CulturaLinkedData took 0.26946449279785156s
Performance | Throughput check for CulturaLinkedData took 11.467780590057373s
Amount of data | Check the number of entities for CulturaLinkedData took 7.05718994140625e-05s
Verifiability | Contribs. check for CulturaLinkedData took 0.2603037357330322s
Interlinking | sameAs chians check for CulturaLinkedData took 0.3825657367706299s
Interlinking | skos check for CulturaLinkedData took 0.5114011764526367s
Interlinking | skos check for CulturaLinkedData took 0.16708922386169434s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.3513784408569336s
Currency | Creation date check for CulturaLinkedData took 0.42676782608032227s
Currency | Modification date check for CulturaLinkedData took 0.3394002914428711s
Rep.Conc. | URIs length for CulturaLinkedData took 52.01024055480957s
Interoperability | New vocabularies check for CulturaLinkedData took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.16396260261535645s
Accuracy | Check Functional Property for CulturaLinkedData took 0.16977643966674805s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.17281150817871094s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 39.77979302406311s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.5824358463287354s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.2865474224090576s
Consistency | Disjoint class check for CulturaLinkedData took 0.2001485824584961s
Consistency | Check Misplaced properties for CulturaLinkedData took 9.05494737625122s
Consistency | Misplaced classes for CulturaLinkedData took 4.14117956161499s
Consistency | Check Ontology hijacking for CulturaLinkedData took 39.688854694366455s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.348539113998413s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 10.371285200119019s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3774051666259766s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.17067384719848633s
Security | Sign check for CulturaLinkedData took 1.044518232345581s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 10.342377424240112s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.37279295921325684s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.021188735961914062s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 2.384185791015625e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.0251998901367188e-05s
INFO | --- Analysis for culturalinkeddata took 544.1761846542358s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.1985635757446289s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2685070037841797s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.021221637725830078s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.8623809814453125e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-ares-or took 2.8838133811950684s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.1196126937866211s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.262326717376709s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.021217823028564453s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.62396240234375e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 7.867813110351562e-06s
INFO | --- Analysis for cz-ares-rzp took 2.7678771018981934s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.0996389389038086s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.2690110206604004s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.021883726119995117s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.6716461181640625e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 9.5367431640625e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 2.924922227859497s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.09969687461853027s
Availability | VoID file availability check for Integrated pollution registry took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.2643280029296875s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.02097010612487793s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.9577484130859375e-05s
Believability | Calculation of trust value for Integrated pollution registry took 8.58306884765625e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.8075954914093018s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.10027456283569336s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.2609717845916748s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.0218813419342041s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0008041858673095703s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 7.033348083496094e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 4.76837158203125e-06s
INFO | --- Analysis for cz-contracts took 2.76245379447937s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.0998990535736084s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.26844215393066406s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020830392837524414s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.552436828613281e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 8.106231689453125e-06s
INFO | --- Analysis for cz-ctia-bans took 7.439202308654785s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.09848546981811523s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.2696411609649658s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.021648406982421875s
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.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.5762786865234375e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 8.106231689453125e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.7444283962249756s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.09969186782836914s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.2632441520690918s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.02284860610961914s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.790855407714844e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 8.344650268554688e-06s
INFO | --- Analysis for cz-ctia-focus took 2.7487423419952393s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.09923529624938965s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0013439655303955078s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.26915717124938965s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020850658416748047s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.38690185546875e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 7.3909759521484375e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.7447926998138428s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.09908485412597656s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.27794575691223145s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.021033048629760742s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.600120544433594e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 9.059906005859375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 8.974535942077637s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.1467137336730957s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0007240772247314453s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.27112698554992676s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.021818161010742188s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.790855407714844e-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 2.8421173095703125s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.09878802299499512s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.2697136402130127s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.0208437442779541s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.504753112792969e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 7.867813110351562e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 2.8083295822143555s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.5447745323181152s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.26537227630615234s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.02198624610900879s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.814697265625e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.3838605880737305s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.31769847869873047s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.26937127113342285s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020831823348999023s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.122915744781494s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.3141801357269287s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.26853489875793457s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.022603988647460938s
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.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.910064697265625e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 8.58306884765625e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.1180248260498047s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.31744813919067383s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.27182865142822266s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.020777225494384766s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.8623809814453125e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 1.33514404296875e-05s
INFO | --- Analysis for cz-czso-job-applicants took 3.1893374919891357s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.31725192070007324s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.2757565975189209s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.02094101905822754s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.981590270996094e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.1943624019622803s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3175034523010254s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0008766651153564453s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.27219057083129883s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.02065134048461914s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.528594970703125e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 9.775161743164062e-06s
INFO | --- Analysis for cz-czso-regions took 2.9736721515655518s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.31782960891723633s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0002963542938232422s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.27296972274780273s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.0211181640625s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.161503791809082s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.31494832038879395s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2631509304046631s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020819425582885742s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.029273986816406e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 7.867813110351562e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.1669058799743652s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.31684422492980957s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2591109275817871s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.981590270996094e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 4.0531158447265625e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.1401944160461426s
Availability | SPARQL endpoint availability check for ATC groups took 0.0986020565032959s
Availability | VoID file availability check for ATC groups took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for ATC groups took 0.2709846496582031s
Reputation | Calculation of the PageRank for ATC groups took 0.020994901657104492s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for ATC groups took 6.937980651855469e-05s
Believability | Calculation of trust value for ATC groups took 9.775161743164062e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.7823386192321777s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10117721557617188s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.2740309238433838s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.02463674545288086s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0011932849884033203s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 5.0067901611328125e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 5.4836273193359375e-06s
INFO | --- Analysis for cz-fulfillments took 2.7756171226501465s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.02063584327697754s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.2832963466644287s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.022169828414916992s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.982948303222656e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 9.059906005859375e-06s
INFO | --- Analysis for cz-ic took 3.061190366744995s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.10950613021850586s
Availability | VoID file availability check for List of Czech data boxes took 0.000728607177734375s
Extra | Recovery of all triples for List of Czech data boxes took 144.57233142852783s
Performance | Total latancy measurement for List of Czech data boxes took 0.5257880687713623s
Amount of data | Number of triples check for List of Czech data boxes took 11.004685401916504s
Interoperability | New terms check for List of Czech data boxes took 10.61215591430664s
Versatility | Languages check for List of Czech data boxes took 300.15959119796753s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.3001010417938232s
Interpretability | RDF structures check for List of Czech data boxes took 0.13828539848327637s
Versatility | Serialization formats check for List of Czech data boxes took 0.15695905685424805s
Availability | RDF dump link check for List of Czech data boxes took 13.811472177505493s
License | MR license check for List of Czech data boxes took 0.27608203887939453s
License | HR license check for List of Czech data boxes took 58.0232195854187s
Amount of data | Number of property check for List of Czech data boxes took 0.11187171936035156s
Understandability | Number of label check for List of Czech data boxes took 1.3394019603729248s
Understandability | URI regex check for List of Czech data boxes took 0.4237024784088135s
Understandability | Vocabs check for List of Czech data boxes took 0.10812830924987793s
Verifiability | Authors check for List of Czech data boxes took 0.1137392520904541s
Verifiability | Publishers check for List of Czech data boxes took 0.10419321060180664s
Performance | Throughput check for List of Czech data boxes took 10.843578577041626s
Amount of data | Check the number of entities for List of Czech data boxes took 2.8775413036346436s
Verifiability | Contribs. check for List of Czech data boxes took 0.12033748626708984s
Interlinking | sameAs chians check for List of Czech data boxes took 0.4389941692352295s
Interlinking | skos check for List of Czech data boxes took 0.1770939826965332s
Interlinking | skos check for List of Czech data boxes took 0.10013222694396973s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.22042202949523926s
Currency | Creation date check for List of Czech data boxes took 0.2130284309387207s
Currency | Modification date check for List of Czech data boxes took 0.10412311553955078s
Rep.Conc. | URIs length for List of Czech data boxes took 113.68189978599548s
Interoperability | New vocabularies check for List of Czech data boxes took 29.538549184799194s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.3371868133544922s
Accuracy | Check Functional Property for List of Czech data boxes took 0.17766404151916504s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.1813831329345703s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 32.8109986782074s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.0199408531188965s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.5836429595947266s
Consistency | Disjoint class check for List of Czech data boxes took 0.10156583786010742s
Consistency | Check Misplaced properties for List of Czech data boxes took 68.94108557701111s
Consistency | Misplaced classes for List of Czech data boxes took 7.3555216789245605s
Consistency | Check Ontology hijacking for List of Czech data boxes took 33.8257851600647s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.3548648357391357s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 64.58814859390259s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.5773355960845947s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.34165263175964355s
Security | Sign check for List of Czech data boxes took 0.13450407981872559s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 378.04438734054565s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.5074801445007324s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.02130722999572754s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 3.647804260253906e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 8.893601179122925s
Believability | Calculation of trust value for List of Czech data boxes took 5.0067901611328125e-06s
INFO | --- Analysis for cz-list-of-databoxes took 1640.5143604278564s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10802197456359863s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0005877017974853516s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 153.94225454330444s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4899468421936035s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.597997188568115s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.843420028686523s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.1685836315155s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.13814377784729s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11918878555297852s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.15801024436950684s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 13.998415231704712s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10677194595336914s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 54.38568902015686s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10465669631958008s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4593675136566162s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4259481430053711s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10262155532836914s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11539745330810547s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10499739646911621s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.781444787979126s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.10717511177063s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10435748100280762s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.27883338928222656s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17819547653198242s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10533690452575684s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1040496826171875s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.21453142166137695s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10751581192016602s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 115.17351841926575s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 926.3938460350037s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4014155864715576s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1439201831817627s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1407766342163086s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 32.50701403617859s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.022845983505249s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6309151649475098s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10679960250854492s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 68.9338071346283s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.500149726867676s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 31.914660215377808s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4174284934997559s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 64.96587944030762s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6160929203033447s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3328089714050293s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13130998611450195s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 377.98418736457825s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4328465461730957s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.02144789695739746s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.86102294921875e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 30.521543741226196s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.0067901611328125e-06s
INFO | --- Analysis for cz-nace took 2564.593401193619s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2782857418060303s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0005328655242919922s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.1 took 433.44120812416077s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.7713911533355713s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.911083459854126s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.4335858821868896s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.1 took 300.16631412506104s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.4748427867889404s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.87068772315979s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.1 took 6.616001844406128s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.31342077255249023s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.7685694694519043s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.3503062725067139s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.15471649169921875s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.5280585289001465s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.43053483963012695s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.21870827674865723s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.43970727920532227s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.27836155891418457s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.1 took 10.27364730834961s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.1 took 7.534027099609375e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.19158005714416504s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.19451308250427246s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.5013432502746582s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.15313386917114258s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.480384111404419s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.5474958419799805s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3777282238006592s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.1 took 92.64960145950317s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.1 took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.14509010314941406s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3824012279510498s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.38536882400512695s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.1 took 72.04180669784546s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.36659836769104s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.65832781791687s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.21138477325439453s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.264314651489258s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 7.96224045753479s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.1 took 76.15941214561462s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.7772021293640137s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.684081077575684s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.1029059886932373s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2674233913421631s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.33486485481262207s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.1 took 939.7055070400238s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.6187324523925781s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.022669076919555664s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.602836608886719e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.9073486328125e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.5497207641601562e-05s
INFO | --- Analysis for cz-nkod took 24998.269406557083s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.18741846084594727s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.00087738037109375s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.265887975692749s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.02112579345703125s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 4.0531158447265625e-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 2.8292624950408936s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.17485547065734863s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0005373954772949219s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 143.0529956817627s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.5182702541351318s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 10.378432750701904s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 11.067059755325317s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.1511900424957s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.2042999267578125s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.11493945121765137s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.14751625061035156s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 13.559668064117432s
License | MR license check for Institutions of public power of the Czech Republic took 0.10227584838867188s
License | HR license check for Institutions of public power of the Czech Republic took 54.13672852516174s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.10824060440063477s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.600757360458374s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.3761625289916992s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.10200095176696777s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.10994625091552734s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.11040163040161133s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.78721308708191s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 2.989778757095337s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.10956692695617676s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.4149491786956787s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.17244672775268555s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.10374617576599121s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.2116718292236328s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.22838687896728516s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.10811257362365723s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 114.73863744735718s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 478.3469376564026s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.3577702045440674s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.2046952247619629s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.1992020606994629s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 32.390690088272095s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 2.997361421585083s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.598433017730713s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.10360360145568848s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 68.40782308578491s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.442652702331543s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 32.345958948135376s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.3982949256896973s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 63.630345582962036s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.583630323410034s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.3300604820251465s
Security | Sign check for Institutions of public power of the Czech Republic took 0.11346578598022461s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 375.89397644996643s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.4942328929901123s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.022286653518676758s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 884.7549335956573s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 1.1444091796875e-05s
INFO | --- Analysis for cz-ovm took 2953.369244337082s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.10132074356079102s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.26413750648498535s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.021914958953857422s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-ovm-agendas took 2.7826452255249023s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.16224050521850586s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0005962848663330078s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 56.17523550987244s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.49393296241760254s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 32.30658507347107s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 33.25692057609558s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.11917757987976s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11412382125854492s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6593847274780273s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12728118896484375s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7144701480865479s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.15324616432189941s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1044914722442627s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10362529754638672s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.9399547576904297s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.20535540580749512s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12072300910949707s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.19898223876953125s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1029057502746582s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.075317621231079s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.081031799316406e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10413742065429688s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10286402702331543s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12347650527954102s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10123205184936523s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10509490966796875s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.20619940757751465s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1031498908996582s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 279.085675239563s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13074445724487305s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12181544303894043s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11910891532897949s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 13.128732919692993s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.146219491958618s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.650247097015381s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11869931221008301s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 168.21346926689148s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.695441484451294s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 17.320945024490356s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.2734417915344238s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 169.35749983787537s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 3.0091261863708496s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.3141319751739502s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10694360733032227s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.728408575057983s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6029233932495117s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.022362470626831055s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.700920104980469e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.430511474609375e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-ruian took 1581.8425996303558s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.6293864250183105s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0006799697875976562s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.29935717582702637s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020786762237548828s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.176399230957031e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 7.867813110351562e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 3.6901450157165527s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.40162038803100586s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.26334667205810547s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020809173583984375s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 4.1484832763671875e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.3914976119995117s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.3997917175292969s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.2621190547943115s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.022342205047607422s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.170967102050781e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 1.049041748046875e-05s
INFO | --- Analysis for cz-sao-check-actions-law took 3.3893871307373047s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10011672973632812s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.2590172290802002s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.147125244140625e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-sidc-drug-ingredients took 2.741360664367676s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.09924125671386719s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.2677016258239746s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.0517578125e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.7476956844329834s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.09861946105957031s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.2650160789489746s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020694732666015625s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.409385681152344e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.1920928955078125e-05s
INFO | --- Analysis for cz-sidc-drugs took 2.8068087100982666s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.17551326751708984s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0005958080291748047s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 144.4672248363495s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5206937789916992s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 10.99593186378479s
Interoperability | New terms check for Summary types of Czech institutions of public power took 11.49004578590393s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.1414167881012s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.229689121246338s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.10104966163635254s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.14848804473876953s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 13.209102392196655s
License | MR license check for Summary types of Czech institutions of public power took 0.1013021469116211s
License | HR license check for Summary types of Czech institutions of public power took 56.209322690963745s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.11026692390441895s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.5476646423339844s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.4260404109954834s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.10735630989074707s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.11096882820129395s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.10208487510681152s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.741517782211304s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.0964419841766357s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.10796093940734863s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.3713958263397217s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.15262794494628906s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.1072242259979248s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.24497699737548828s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.21849846839904785s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.10392642021179199s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 114.22518658638s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 17.82071852684021s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.33719420433044434s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.18477940559387207s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.18666982650756836s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 31.735880136489868s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.012181282043457s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.6102728843688965s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.10788273811340332s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 69.35134267807007s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.379926681518555s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 31.886207580566406s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.2495205402374268s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 63.03459978103638s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.579606056213379s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.3399498462677002s
Security | Sign check for Summary types of Czech institutions of public power took 0.1307077407836914s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 368.5803530216217s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.34474968910217285s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.021585464477539062s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.601478576660156e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 46.5756413936615s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 9.298324584960938e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 1648.9709284305573s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.10337305068969727s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.26207566261291504s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020931482315063477s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.2901763916015625e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 8.106231689453125e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 2.7480366230010986s
Availability | SPARQL endpoint availability check for State funding providers took 0.09587955474853516s
Availability | VoID file availability check for State funding providers took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for State funding providers took 0.2663602828979492s
Reputation | Calculation of the PageRank for State funding providers took 0.020888328552246094s
Interlinking | Calculation of Degree of Connection for State funding providers took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for State funding providers took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.7670135498046875e-05s
Believability | Calculation of trust value for State funding providers took 5.9604644775390625e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 2.715588331222534s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.09990739822387695s
Availability | VoID file availability check for Organizations active in R&D took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.2665367126464844s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020941495895385742s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 3.790855407714844e-05s
Believability | Calculation of trust value for Organizations active in R&D took 8.344650268554688e-06s
INFO | --- Analysis for cz-vavai-organizations took 2.912595748901367s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.09990572929382324s
Availability | VoID file availability check for R&D Programmes took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.27150726318359375s
Reputation | Calculation of the PageRank for R&D Programmes took 0.02052927017211914s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 3.910064697265625e-05s
Believability | Calculation of trust value for R&D Programmes took 8.344650268554688e-06s
INFO | --- Analysis for cz-vavai-programmes took 2.7957966327667236s
Availability | SPARQL endpoint availability check for R&D Projects took 0.09896492958068848s
Availability | VoID file availability check for R&D Projects took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.27375125885009766s
Reputation | Calculation of the PageRank for R&D Projects took 0.022252321243286133s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 3.814697265625e-05s
Believability | Calculation of trust value for R&D Projects took 8.106231689453125e-06s
INFO | --- Analysis for cz-vavai-projects took 2.755333662033081s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.10039854049682617s
Availability | VoID file availability check for Institutional research plans took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.26523494720458984s
Reputation | Calculation of the PageRank for Institutional research plans took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 3.838539123535156e-05s
Believability | Calculation of trust value for Institutional research plans took 7.62939453125e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.823291778564453s
Availability | SPARQL endpoint availability check for Results of R&D took 0.09905576705932617s
Availability | VoID file availability check for Results of R&D took 0.0007078647613525391s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.27681803703308105s
Reputation | Calculation of the PageRank for Results of R&D took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Results of R&D took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 3.814697265625e-05s
Believability | Calculation of trust value for Results of R&D took 7.62939453125e-06s
INFO | --- Analysis for cz-vavai-results took 2.76493763923645s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.09982752799987793s
Availability | VoID file availability check for Tenders in R&D took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.2622559070587158s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.02133011817932129s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 3.933906555175781e-05s
Believability | Calculation of trust value for Tenders in R&D took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.794224500656128s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.649162292480469e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.2688305377960205s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020802974700927734s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.5762786865234375e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.0251998901367188e-05s
INFO | --- Analysis for czech_addresses took 3.801994562149048s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.6232028007507324s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.26934146881103516s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.02062535285949707s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.4809112548828125e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for DanteLatinLoanwords took 4.1753528118133545s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.35123372077941895s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0006544589996337891s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 120.34579491615295s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 0.8986060619354248s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 3.4184958934783936s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.186593294143677s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.29417729377747s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.20576739311218262s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.10581421852111816s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.5026993751525879s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.2172832489013672s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.20314717292785645s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.22321820259094238s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.29792404174805s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.20683717727661133s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 1.2413392066955566s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.4028589725494385s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.21210980415344238s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.20432114601135254s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.20862603187561035s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 10.649060487747192s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.748603820800781e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.2158510684967041s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.9223039150238037s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.3082349300384521s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.21614503860473633s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.2325420379638672s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 1.2480976581573486s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 1.4835906028747559s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 82.44968032836914s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.19467520713806152s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.2822432518005371s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.3010976314544678s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 37.5416898727417s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.093369722366333s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.614750862121582s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.27573299407958984s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 22.334054231643677s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 7.458044052124023s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 38.12936472892761s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.4246773719787598s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 21.18111538887024s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.763289213180542s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.2210988998413086s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.2204899787902832s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 9.82529902458191s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.4029688835144043s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.02172994613647461s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014710426330566406s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.6689300537109375e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.2159347534179688e-05s
INFO | --- Analysis for data-bnf-fr took 824.2361149787903s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 15.028944730758667s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.2633934020996094s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.02199387550354004s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 6.794929504394531e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 9.059906005859375e-06s
INFO | --- Analysis for data-cnr-it took 67.78308939933777s
Availability | SPARQL endpoint availability check for Data.gov took 1.0218241214752197s
Availability | VoID file availability check for Data.gov took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Data.gov took 0.26339268684387207s
Reputation | Calculation of the PageRank for Data.gov took 0.021392345428466797s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.170967102050781e-05s
Believability | Calculation of trust value for Data.gov took 9.775161743164062e-06s
INFO | --- Analysis for data-gov took 16.124855041503906s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.029552221298217773s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.2542867660522461s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.02108597755432129s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.05718994140625e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 4.291534423828125e-06s
INFO | --- Analysis for data-gov-ie took 2.4299187660217285s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 9.036064147949219e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.00022292137145996094s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.26001763343811035s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.081031799316406e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 4.0531158447265625e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.4075210094451904s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 19.492674112319946s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0006103515625s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.27225279808044434s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02094554901123047s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.866455078125e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 1.0251998901367188e-05s
INFO | --- Analysis for data-hnm-hu took 165.44459438323975s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.08403635025024414s
Availability | VoID file availability check for Climb Dataincubator took 0.0003819465637207031s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.26276445388793945s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.0224306583404541s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0008747577667236328s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 8.630752563476562e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.1682510375976562e-05s
INFO | --- Analysis for data-incubator-climb took 2.586759567260742s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.1961669921875e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.2697329521179199s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.0215609073638916s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.655952453613281e-05s
Believability | Calculation of trust value for Discogs in RDF took 1.1920928955078125e-05s
INFO | --- Analysis for data-incubator-discogs took 4.593801498413086s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.13124632835388184s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0007977485656738281s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.27422523498535156s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.022366762161254883s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.412101745605469e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 9.5367431640625e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.279236316680908s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.051639556884765625s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.26705455780029297s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.021157026290893555s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 9.107589721679688e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 1.1920928955078125e-05s
INFO | --- Analysis for data-incubator-moseley took 7.518212556838989s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.04943513870239258s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.26662611961364746s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020923376083374023s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 9.083747863769531e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.1444091796875e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 2.760789394378662s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.4412877559661865s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.27004575729370117s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.0212404727935791s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.702278137207031e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 8.821487426757812e-06s
INFO | --- Analysis for data-incubator-nasa took 6.91815710067749s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.05304837226867676s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00021910667419433594s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.26199841499328613s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.02106475830078125s
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.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.62939453125e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 9.059906005859375e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.5239744186401367s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.050896406173706055s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.27494215965270996s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.021706342697143555s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 0.000110626220703125s
Believability | Calculation of trust value for Pokedex data in RDF took 1.1920928955078125e-05s
INFO | --- Analysis for data-incubator-pokedex took 3.2467904090881348s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.04491305351257324s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.2701089382171631s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.021061182022094727s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.869171142578125e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.2636184692382812e-05s
INFO | --- Analysis for data-incubator-smcjournals took 2.477135181427002s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.46996450424194336s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006220340728759766s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 13.717183828353882s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.2175400257110596s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 20.628909826278687s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.5077226161956787s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.288471937179565s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.28839659690857s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.14074945449829102s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.46190857887268066s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.6094257831573486s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.309506893157959s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.43872594833374023s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.305341482162476s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.618027925491333s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 26.22962236404419s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.6860649585723877s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.3358340263366699s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.5226073265075684s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.34609317779541016s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 11.363694190979004s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 6.4849853515625e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.36049318313598633s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.985515832901001s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.4480092525482178s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.4205286502838135s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.44188785552978516s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.7346081733703613s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.7962348461151123s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 33.36048460006714s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.3552286624908447s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.29413414001464844s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.32285356521606445s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 31.66939687728882s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 2.9296844005584717s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.1115992069244385s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.3529036045074463s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 1.3571703433990479s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 7.946350336074829s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 25.218793630599976s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.3786077499389648s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 4.324812889099121s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.8083484172821045s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.5119819641113281s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.36452150344848633s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.10894322395324707s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.2915482521057129s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.020536422729492188s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.794929504394531e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 1.6689300537109375e-06s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 1.0967254638671875e-05s
INFO | --- Analysis for data-open-ac-uk took 645.8049857616425s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.7006595134735107s
Availability | VoID file availability check for Persée in RDF took 0.0006756782531738281s
Extra | Recovery of all triples for Persée in RDF took 1.1546380519866943s
Performance | Total latancy measurement for Persée in RDF took 0.5795679092407227s
Amount of data | Number of triples check for Persée in RDF took 1.3790793418884277s
Interoperability | New terms check for Persée in RDF took 1.867776870727539s
Versatility | Languages check for Persée in RDF took 121.48172092437744s
Interpretability | Number of blank nodes check for Persée in RDF took 0.4353632926940918s
Interpretability | RDF structures check for Persée in RDF took 0.8534119129180908s
Versatility | Serialization formats check for Persée in RDF took 1.0676610469818115s
Availability | RDF dump link check for Persée in RDF took 0.2984020709991455s
License | MR license check for Persée in RDF took 1.6774201393127441s
License | HR license check for Persée in RDF took 40.36924362182617s
Amount of data | Number of property check for Persée in RDF took 0.12960171699523926s
Understandability | Number of label check for Persée in RDF took 2.1753146648406982s
Understandability | URI regex check for Persée in RDF took 0.9170267581939697s
Understandability | Vocabs check for Persée in RDF took 0.43752145767211914s
Verifiability | Authors check for Persée in RDF took 0.13005971908569336s
Verifiability | Publishers check for Persée in RDF took 0.11688399314880371s
Performance | Throughput check for Persée in RDF took 10.612518072128296s
Amount of data | Check the number of entities for Persée in RDF took 0.00011682510375976562s
Verifiability | Contribs. check for Persée in RDF took 0.12149834632873535s
Interlinking | sameAs chians check for Persée in RDF took 0.21670198440551758s
Interlinking | skos check for Persée in RDF took 0.7652618885040283s
Interlinking | skos check for Persée in RDF took 0.11983036994934082s
Timeliness | dataset update frequency check for Persée in RDF took 0.7371904850006104s
Currency | Creation date check for Persée in RDF took 0.5866756439208984s
Currency | Modification date check for Persée in RDF took 0.2437131404876709s
Rep.Conc. | URIs length for Persée in RDF took 3.746959686279297s
Interoperability | New vocabularies check for Persée in RDF took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.11639690399169922s
Accuracy | Check Functional Property for Persée in RDF took 0.13080072402954102s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.1334235668182373s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.8864860534667969s
Accuracy | Check White space in annotation for Persée in RDF took 0.039598941802978516s
Accuracy | Check Datatype consistency for Persée in RDF took 0.027554035186767578s
Consistency | Disjoint class check for Persée in RDF took 0.2986435890197754s
Consistency | Check Misplaced properties for Persée in RDF took 2.6134305000305176s
Consistency | Misplaced classes for Persée in RDF took 0.21068668365478516s
Consistency | Check Ontology hijacking for Persée in RDF took 1.8030273914337158s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.3106882572174072s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.8523693084716797s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.03215289115905762s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.12378907203674316s
Security | Sign check for Persée in RDF took 0.848618745803833s
Availability | Check URIs Dereferenciability for Persée in RDF took 1276.238263130188s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.3498666286468506s
Reputation | Calculation of the PageRank for Persée in RDF took 0.021677017211914062s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.0001163482666015625s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 3.337860107421875e-06s
Believability | Calculation of trust value for Persée in RDF took 1.0728836059570312e-05s
INFO | --- Analysis for data-persee-fr took 1519.6618399620056s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 0.9987015724182129s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.2722940444946289s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020686626434326172s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011181831359863281s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 6.67572021484375e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 8.218639373779297s
Availability | SPARQL endpoint availability check for Open Data Web took 13.621413946151733s
Availability | VoID file availability check for Open Data Web took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.27372050285339355s
Reputation | Calculation of the PageRank for Open Data Web took 0.020740032196044922s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 2.9802322387695312e-05s
Believability | Calculation of trust value for Open Data Web took 1.049041748046875e-05s
INFO | --- Analysis for data.odw.tw took 22.43682050704956s
Availability | SPARQL endpoint availability check for datahub took 9.059906005859375e-05s
Availability | VoID file availability check for datahub took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for datahub took 0.27602410316467285s
Reputation | Calculation of the PageRank for datahub took 0.020851850509643555s
Interlinking | Calculation of Degree of Connection for datahub took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for datahub took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for datahub took 4.458427429199219e-05s
Believability | Calculation of trust value for datahub took 1.0013580322265625e-05s
INFO | --- Analysis for datahub took 4.073843955993652s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 5.896231174468994s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0007262229919433594s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.27086782455444336s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020838499069213867s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.123283386230469e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 1.1205673217773438e-05s
INFO | --- Analysis for datahub-kr-datamap took 14.218522548675537s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.33243656158447266s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.270845890045166s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.020610570907592773s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 6.818771362304688e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.1920928955078125e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 4.819476366043091s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.086808443069458s
Availability | VoID file availability check for datos-artium-org took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.27297234535217285s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020604848861694336s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011587142944335938s
Believability | Calculation of trust value for datos-artium-org took 1.1205673217773438e-05s
INFO | --- Analysis for datos-artium-org took 164.51795077323914s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.793720006942749s
Availability | VoID file availability check for Datos.bcn.cl took 0.0006470680236816406s
Extra | Recovery of all triples for Datos.bcn.cl took 22.325502157211304s
Performance | Total latancy measurement for Datos.bcn.cl took 5.9572789669036865s
Amount of data | Number of triples check for Datos.bcn.cl took 4.488067388534546s
Interoperability | New terms check for Datos.bcn.cl took 3.527168035507202s
Versatility | Languages check for Datos.bcn.cl took 301.03444719314575s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.2538161277770996s
Security | Check HTTPS for Datos.bcn.cl took 0.7269613742828369s
Interpretability | RDF structures check for Datos.bcn.cl took 1.2785720825195312s
Versatility | Serialization formats check for Datos.bcn.cl took 1.228916883468628s
Availability | RDF dump link check for Datos.bcn.cl took 1.1779749393463135s
License | MR license check for Datos.bcn.cl took 1.2115747928619385s
License | HR license check for Datos.bcn.cl took 45.275131702423096s
Amount of data | Number of property check for Datos.bcn.cl took 1.231884241104126s
Understandability | Number of label check for Datos.bcn.cl took 1.3916704654693604s
Understandability | URI regex check for Datos.bcn.cl took 2.403315305709839s
Understandability | Vocabs check for Datos.bcn.cl took 1.2060267925262451s
Verifiability | Authors check for Datos.bcn.cl took 1.1861732006072998s
Verifiability | Publishers check for Datos.bcn.cl took 1.2013583183288574s
Performance | Throughput check for Datos.bcn.cl took 11.909939289093018s
Amount of data | Check the number of entities for Datos.bcn.cl took 6.961822509765625e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.1984612941741943s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.1988096237182617s
Interlinking | skos check for Datos.bcn.cl took 1.2098426818847656s
Interlinking | skos check for Datos.bcn.cl took 1.1992769241333008s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.2032389640808105s
Currency | Creation date check for Datos.bcn.cl took 2.384247303009033s
Currency | Modification date check for Datos.bcn.cl took 1.1910438537597656s
Rep.Conc. | URIs length for Datos.bcn.cl took 18.317031860351562s
Interoperability | New vocabularies check for Datos.bcn.cl took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.1926507949829102s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.184516191482544s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.1989657878875732s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 11.330981254577637s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.31855297088623047s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.2717602252960205s
Consistency | Disjoint class check for Datos.bcn.cl took 1.1967856884002686s
Consistency | Check Misplaced properties for Datos.bcn.cl took 7.47161078453064s
Consistency | Misplaced classes for Datos.bcn.cl took 2.0003769397735596s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 10.116695642471313s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.2545440196990967s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 7.004911661148071s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.2985270023345947s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.4398162364959717s
Security | Sign check for Datos.bcn.cl took 1.2060208320617676s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 7775.870450496674s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.5965225696563721s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.021592378616333008s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.724761962890625e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.9073486328125e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 9.059906005859375e-06s
INFO | --- Analysis for datos-bcn-cl took 8567.433248758316s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.47306013107299805s
Availability | VoID file availability check for datos.bne.es took 0.0006377696990966797s
Extra | Recovery of all triples for datos.bne.es took 134.80970072746277s
Performance | Total latancy measurement for datos.bne.es took 1.26127028465271s
Amount of data | Number of triples check for datos.bne.es took 0.875389814376831s
Interoperability | New terms check for datos.bne.es took 2.3142263889312744s
Versatility | Languages check for datos.bne.es took 60.64299702644348s
Interpretability | Number of blank nodes check for datos.bne.es took 0.2876420021057129s
Security | Check HTTPS for datos.bne.es took 0.1680431365966797s
Interpretability | RDF structures check for datos.bne.es took 0.6257195472717285s
Versatility | Serialization formats check for datos.bne.es took 0.6413233280181885s
Availability | RDF dump link check for datos.bne.es took 0.3583195209503174s
License | MR license check for datos.bne.es took 0.8645713329315186s
License | HR license check for datos.bne.es took 61.20890522003174s
Amount of data | Number of property check for datos.bne.es took 0.2837226390838623s
Understandability | Number of label check for datos.bne.es took 1.1618354320526123s
Understandability | URI regex check for datos.bne.es took 0.7508983612060547s
Understandability | Vocabs check for datos.bne.es took 0.34804654121398926s
Verifiability | Authors check for datos.bne.es took 0.3967475891113281s
Verifiability | Publishers check for datos.bne.es took 0.3443751335144043s
Performance | Throughput check for datos.bne.es took 11.645083904266357s
Amount of data | Check the number of entities for datos.bne.es took 6.103515625e-05s
Verifiability | Contribs. check for datos.bne.es took 0.3533635139465332s
Interlinking | sameAs chians check for datos.bne.es took 0.4426867961883545s
Interlinking | skos check for datos.bne.es took 0.5958359241485596s
Interlinking | skos check for datos.bne.es took 0.2522456645965576s
Timeliness | dataset update frequency check for datos.bne.es took 0.41709017753601074s
Currency | Creation date check for datos.bne.es took 0.6440243721008301s
Currency | Modification date check for datos.bne.es took 0.5710873603820801s
Rep.Conc. | URIs length for datos.bne.es took 50.75869798660278s
Interoperability | New vocabularies check for datos.bne.es took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 0.27317070960998535s
Accuracy | Check Functional Property for datos.bne.es took 0.2810187339782715s
Accuracy | Check Inverse Functional Property for datos.bne.es took 0.40619444847106934s
Accuracy | Check Empty annotation labels for datos.bne.es took 39.45933413505554s
Accuracy | Check White space in annotation for datos.bne.es took 1.6038200855255127s
Accuracy | Check Datatype consistency for datos.bne.es took 1.3011822700500488s
Consistency | Disjoint class check for datos.bne.es took 0.30823445320129395s
Consistency | Check Misplaced properties for datos.bne.es took 9.019515037536621s
Consistency | Misplaced classes for datos.bne.es took 4.298590898513794s
Consistency | Check Ontology hijacking for datos.bne.es took 42.68967962265015s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.1765737533569336s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 10.49076795578003s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.3436305522918701s
Conciseness | Check Intensional conciseness for datos.bne.es took 0.28371572494506836s
Security | Sign check for datos.bne.es took 1.125830888748169s
Availability | Check URIs Dereferenciability for datos.bne.es took 9.914897441864014s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.45415592193603516s
Reputation | Calculation of the PageRank for datos.bne.es took 0.02112722396850586s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011992454528808594s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 1.6689300537109375e-06s
Believability | Calculation of trust value for datos.bne.es took 1.0728836059570312e-05s
INFO | --- Analysis for datos-bne-es took 551.5477206707001s
Availability | SPARQL endpoint availability check for dbacademic took 0.048688650131225586s
Availability | VoID file availability check for dbacademic took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for dbacademic took 0.27195167541503906s
Reputation | Calculation of the PageRank for dbacademic took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for dbacademic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for dbacademic took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for dbacademic took 2.956390380859375e-05s
Believability | Calculation of trust value for dbacademic took 8.58306884765625e-06s
INFO | --- Analysis for dbacademic took 2.545722246170044s
Availability | SPARQL endpoint availability check for DBkWik took 15.168181896209717s
Availability | VoID file availability check for DBkWik took 0.000576019287109375s
Extra | Recovery of all triples for DBkWik took 1.4366350173950195s
Performance | Total latancy measurement for DBkWik took 19.196436405181885s
Amount of data | Number of triples check for DBkWik took 5.276687383651733s
Interoperability | New terms check for DBkWik took 40.4260311126709s
Versatility | Languages check for DBkWik took 62.71009922027588s
Interpretability | Number of blank nodes check for DBkWik took 53.86946940422058s
Interpretability | RDF structures check for DBkWik took 10.068509578704834s
Versatility | Serialization formats check for DBkWik took 4.1501545906066895s
Availability | RDF dump link check for DBkWik took 2.3884735107421875s
License | MR license check for DBkWik took 7.055697917938232s
License | HR license check for DBkWik took 61.308966636657715s
Amount of data | Number of property check for DBkWik took 4.99866247177124s
Understandability | Number of label check for DBkWik took 2.2651548385620117s
Understandability | URI regex check for DBkWik took 5.89958119392395s
Understandability | Vocabs check for DBkWik took 0.3312220573425293s
Verifiability | Authors check for DBkWik took 0.12221980094909668s
Verifiability | Publishers check for DBkWik took 0.09346985816955566s
Performance | Throughput check for DBkWik took 64.06265115737915s
Amount of data | Check the number of entities for DBkWik took 6.723403930664062e-05s
Verifiability | Contribs. check for DBkWik took 0.6889691352844238s
Interlinking | sameAs chians check for DBkWik took 0.4575316905975342s
Interlinking | skos check for DBkWik took 0.49369287490844727s
Interlinking | skos check for DBkWik took 0.0890204906463623s
Timeliness | dataset update frequency check for DBkWik took 0.24059176445007324s
Currency | Creation date check for DBkWik took 0.4655189514160156s
Currency | Modification date check for DBkWik took 0.21423912048339844s
Rep.Conc. | URIs length for DBkWik took 17.44825839996338s
Interoperability | New vocabularies check for DBkWik took 2.253831386566162s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.11268734931945801s
Accuracy | Check Functional Property for DBkWik took 0.301206111907959s
Accuracy | Check Inverse Functional Property for DBkWik took 0.2907254695892334s
Accuracy | Check Empty annotation labels for DBkWik took 1.0406830310821533s
Accuracy | Check White space in annotation for DBkWik took 0.023052215576171875s
Accuracy | Check Datatype consistency for DBkWik took 0.037595510482788086s
Consistency | Disjoint class check for DBkWik took 0.12690305709838867s
Consistency | Check Misplaced properties for DBkWik took 54.742510080337524s
Consistency | Misplaced classes for DBkWik took 7.884246826171875s
Consistency | Check Ontology hijacking for DBkWik took 1.7463586330413818s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.1325361728668213s
Consistency | Check Invalid usage of undefined properties for DBkWik took 33.46730422973633s
Conciseness | Check Extensional conciseness for DBkWik took 0.03188657760620117s
Security | Sign check for DBkWik took 10.000595331192017s
Availability | Check URIs Dereferenciability for DBkWik took 9.65314793586731s
Completeness | Calculation of interlinking completeness for DBkWik took 0.3582758903503418s
Reputation | Calculation of the PageRank for DBkWik took 0.020969390869140625s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.891654968261719e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 3.9755606651306152s
Believability | Calculation of trust value for DBkWik took 1.1205673217773438e-05s
INFO | --- Analysis for dbkwik took 8345.404988527298s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 5.054473876953125e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.26754093170166016s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.020694971084594727s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 3.552436828613281e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00011229515075683594s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.0728836059570312e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 6.5801167488098145s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.2785990238189697s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0005805492401123047s
Extra | Recovery of all triples for dblp Knowledge Graph took 56.539727449417114s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.7383794784545898s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.14977407455444336s
Interoperability | New terms check for dblp Knowledge Graph took 1.6840438842773438s
Versatility | Languages check for dblp Knowledge Graph took 0.1635754108428955s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 4.177471876144409s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.16481590270996094s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.16163992881774902s
Availability | RDF dump link check for dblp Knowledge Graph took 0.12761759757995605s
License | MR license check for dblp Knowledge Graph took 0.1568911075592041s
License | HR license check for dblp Knowledge Graph took 30.125059604644775s
Amount of data | Number of property check for dblp Knowledge Graph took 0.12444829940795898s
Understandability | Number of label check for dblp Knowledge Graph took 0.4240384101867676s
Understandability | URI regex check for dblp Knowledge Graph took 0.25806212425231934s
Understandability | Vocabs check for dblp Knowledge Graph took 0.1380922794342041s
Verifiability | Authors check for dblp Knowledge Graph took 0.1748218536376953s
Verifiability | Publishers check for dblp Knowledge Graph took 0.14217424392700195s
Performance | Throughput check for dblp Knowledge Graph took 10.421467304229736s
Amount of data | Check the number of entities for dblp Knowledge Graph took 7.152557373046875e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.13436007499694824s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.20987820625305176s
Interlinking | skos check for dblp Knowledge Graph took 0.15531587600708008s
Interlinking | skos check for dblp Knowledge Graph took 0.13996458053588867s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.1441636085510254s
Currency | Creation date check for dblp Knowledge Graph took 0.2798469066619873s
Currency | Modification date check for dblp Knowledge Graph took 0.2827444076538086s
Rep.Conc. | URIs length for dblp Knowledge Graph took 27.69001340866089s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.1356344223022461s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.12406253814697266s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.14429187774658203s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 17.191649913787842s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.0829789638519287s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.161229133605957s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.13153076171875s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.2729473114013672s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 18.504133939743042s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 15941.08167719841s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 3.647970199584961s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.6638338565826416s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.14363789558410645s
Security | Sign check for dblp Knowledge Graph took 0.13817620277404785s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 21.714447736740112s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.6218037605285645s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.02164769172668457s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 2.288818359375e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.9073486328125e-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.2636184692382812e-05s
INFO | --- Analysis for dblp-kg took 16203.019807577133s
Availability | SPARQL endpoint availability check for DBnary took 0.24117350578308105s
Availability | VoID file availability check for DBnary took 0.0004565715789794922s
Extra | Recovery of all triples for DBnary took 2.319814920425415s
Performance | Total latancy measurement for DBnary took 0.3261113166809082s
Amount of data | Number of triples check for DBnary took 1.2217800617218018s
Interoperability | New terms check for DBnary took 3.504276990890503s
Versatility | Languages check for DBnary took 62.20965600013733s
Interpretability | Number of blank nodes check for DBnary took 3.9467170238494873s
Security | Check HTTPS for DBnary took 0.1949782371520996s
Interpretability | RDF structures check for DBnary took 0.14432740211486816s
Versatility | Serialization formats check for DBnary took 0.23282980918884277s
Availability | RDF dump link check for DBnary took 0.05955791473388672s
License | MR license check for DBnary took 0.2564055919647217s
License | HR license check for DBnary took 60.449148178100586s
Amount of data | Number of property check for DBnary took 0.09331130981445312s
Understandability | Number of label check for DBnary took 0.8145706653594971s
Understandability | URI regex check for DBnary took 0.12243294715881348s
Understandability | Vocabs check for DBnary took 0.18274760246276855s
Verifiability | Authors check for DBnary took 0.2916295528411865s
Verifiability | Publishers check for DBnary took 0.12379026412963867s
Performance | Throughput check for DBnary took 10.421905517578125s
Amount of data | Check the number of entities for DBnary took 7.462501525878906e-05s
Verifiability | Contribs. check for DBnary took 0.1347668170928955s
Interlinking | sameAs chians check for DBnary took 0.1055154800415039s
Interlinking | skos check for DBnary took 0.28462862968444824s
Interlinking | skos check for DBnary took 0.10631394386291504s
Timeliness | dataset update frequency check for DBnary took 0.1218867301940918s
Currency | Creation date check for DBnary took 0.21135902404785156s
Currency | Modification date check for DBnary took 0.17918944358825684s
Rep.Conc. | URIs length for DBnary took 11.024969816207886s
Interoperability | New vocabularies check for DBnary took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for DBnary took 0.08386659622192383s
Accuracy | Check Functional Property for DBnary took 0.17978763580322266s
Accuracy | Check Inverse Functional Property for DBnary took 0.15740728378295898s
Accuracy | Check Empty annotation labels for DBnary took 0.4453866481781006s
Accuracy | Check White space in annotation for DBnary took 0.02982640266418457s
Accuracy | Check Datatype consistency for DBnary took 0.028160810470581055s
Consistency | Disjoint class check for DBnary took 0.11274147033691406s
Consistency | Check Misplaced properties for DBnary took 8.565528869628906s
Consistency | Misplaced classes for DBnary took 0.21305394172668457s
Consistency | Check Ontology hijacking for DBnary took 1.7952680587768555s
Consistency | Check Invalid usage of undefined classes for DBnary took 1.3666610717773438s
Consistency | Check Invalid usage of undefined properties for DBnary took 9.677636861801147s
Conciseness | Check Extensional conciseness for DBnary took 0.03571367263793945s
Conciseness | Check Intensional conciseness for DBnary took 0.1520063877105713s
Security | Sign check for DBnary took 0.06526374816894531s
Availability | Check URIs Dereferenciability for DBnary took 10.218157052993774s
Completeness | Calculation of interlinking completeness for DBnary took 0.26728081703186035s
Reputation | Calculation of the PageRank for DBnary took 0.021205425262451172s
Interlinking | Calculation of Degree of Connection for DBnary took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for DBnary took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for DBnary took 6.008148193359375e-05s
Interoperability | Check the re-using of existing vocabs for DBnary took 1.430511474609375e-06s
Believability | Calculation of trust value for DBnary took 9.775161743164062e-06s
INFO | --- Analysis for dbnary took 292.71850204467773s
Availability | SPARQL endpoint availability check for DBpedia took 0.849470853805542s
Availability | VoID file availability check for DBpedia took 0.0006499290466308594s
Extra | Recovery of all triples for DBpedia took 6.039396286010742s
Performance | Total latancy measurement for DBpedia took 2.6609878540039062s
Amount of data | Number of triples check for DBpedia took 0.9925522804260254s
Interoperability | New terms check for DBpedia took 5.481503248214722s
Versatility | Languages check for DBpedia took 32.45990228652954s
Interpretability | Number of blank nodes check for DBpedia took 0.5425140857696533s
Security | Check HTTPS for DBpedia took 0.31104326248168945s
Interpretability | RDF structures check for DBpedia took 0.7719309329986572s
Versatility | Serialization formats check for DBpedia took 0.7030482292175293s
Availability | RDF dump link check for DBpedia took 0.5301039218902588s
License | MR license check for DBpedia took 0.7483189105987549s
License | HR license check for DBpedia took 32.48172426223755s
Amount of data | Number of property check for DBpedia took 0.5567991733551025s
Understandability | Number of label check for DBpedia took 4.422882318496704s
Understandability | URI regex check for DBpedia took 1.0639903545379639s
Understandability | Vocabs check for DBpedia took 0.6084063053131104s
Verifiability | Authors check for DBpedia took 0.5959784984588623s
Verifiability | Publishers check for DBpedia took 0.5421717166900635s
Performance | Throughput check for DBpedia took 10.671085834503174s
Amount of data | Check the number of entities for DBpedia took 6.866455078125e-05s
Verifiability | Contribs. check for DBpedia took 0.5494561195373535s
Interlinking | sameAs chians check for DBpedia took 2.5919907093048096s
Interlinking | skos check for DBpedia took 0.8862547874450684s
Interlinking | skos check for DBpedia took 0.5205588340759277s
Timeliness | dataset update frequency check for DBpedia took 0.6532535552978516s
Currency | Creation date check for DBpedia took 1.152700424194336s
Currency | Modification date check for DBpedia took 1.079129934310913s
Rep.Conc. | URIs length for DBpedia took 35.19769096374512s
Interoperability | New vocabularies check for DBpedia took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.532217264175415s
Accuracy | Check Functional Property for DBpedia took 0.5478386878967285s
Accuracy | Check Inverse Functional Property for DBpedia took 0.5541906356811523s
Accuracy | Check Empty annotation labels for DBpedia took 2.132288932800293s
Accuracy | Check White space in annotation for DBpedia took 0.02937006950378418s
Accuracy | Check Datatype consistency for DBpedia took 0.027797698974609375s
Consistency | Disjoint class check for DBpedia took 0.5357346534729004s
Consistency | Check Misplaced properties for DBpedia took 32.396003007888794s
Consistency | Misplaced classes for DBpedia took 3.2776033878326416s
Consistency | Check Ontology hijacking for DBpedia took 4.589737892150879s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.1241295337677002s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.840698003768921s
Conciseness | Check Extensional conciseness for DBpedia took 0.034693241119384766s
Conciseness | Check Intensional conciseness for DBpedia took 2.600283145904541s
Security | Sign check for DBpedia took 0.5735089778900146s
Availability | Check URIs Dereferenciability for DBpedia took 3492.1914451122284s
Completeness | Calculation of interlinking completeness for DBpedia took 0.6422686576843262s
Reputation | Calculation of the PageRank for DBpedia took 0.02129364013671875s
Interlinking | Calculation of Degree of Connection for DBpedia took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0009164810180664062s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia took 6063.991103887558s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 8.7738037109375e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.2907283306121826s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020853519439697266s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.914138793945312e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.0013580322265625e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 7.189329624176025s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.165401458740234s
Availability | VoID file availability check for DBpedia Commons took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.26929783821105957s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.02879500389099121s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.001287698745727539s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 9.942054748535156e-05s
Believability | Calculation of trust value for DBpedia Commons took 1.0251998901367188e-05s
INFO | --- Analysis for dbpedia-commons took 16.445613622665405s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 0.8458971977233887s
Availability | VoID file availability check for DBpedia in Greek took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.28844547271728516s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020867586135864258s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00019025802612304688s
Believability | Calculation of trust value for DBpedia in Greek took 9.059906005859375e-06s
INFO | --- Analysis for dbpedia-el took 6.792328119277954s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.42075276374816895s
Availability | VoID file availability check for DBpedia in Spanish took 0.000621795654296875s
Extra | Recovery of all triples for DBpedia in Spanish took 1854.7820236682892s
Performance | Total latancy measurement for DBpedia in Spanish took 2.4170749187469482s
Amount of data | Number of triples check for DBpedia in Spanish took 6.009703636169434s
Interoperability | New terms check for DBpedia in Spanish took 2.9607579708099365s
Versatility | Languages check for DBpedia in Spanish took 60.62334752082825s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.3922746181488037s
Security | Check HTTPS for DBpedia in Spanish took 2.9794764518737793s
Interpretability | RDF structures check for DBpedia in Spanish took 1.5599768161773682s
Versatility | Serialization formats check for DBpedia in Spanish took 0.7137250900268555s
Availability | RDF dump link check for DBpedia in Spanish took 0.45021700859069824s
License | MR license check for DBpedia in Spanish took 1.517089605331421s
License | HR license check for DBpedia in Spanish took 62.22292637825012s
Amount of data | Number of property check for DBpedia in Spanish took 0.33911871910095215s
Understandability | Number of label check for DBpedia in Spanish took 3.3154990673065186s
Understandability | URI regex check for DBpedia in Spanish took 0.9313461780548096s
Understandability | Vocabs check for DBpedia in Spanish took 0.4439222812652588s
Verifiability | Authors check for DBpedia in Spanish took 0.5452919006347656s
Verifiability | Publishers check for DBpedia in Spanish took 14.61421537399292s
Performance | Throughput check for DBpedia in Spanish took 24.086121320724487s
Amount of data | Check the number of entities for DBpedia in Spanish took 7.343292236328125e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.702176570892334s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.6361000537872314s
Interlinking | skos check for DBpedia in Spanish took 1.5419111251831055s
Interlinking | skos check for DBpedia in Spanish took 0.21389126777648926s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.5159807205200195s
Currency | Creation date check for DBpedia in Spanish took 2.2199971675872803s
Currency | Modification date check for DBpedia in Spanish took 0.6679680347442627s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.391309976577759s
Interoperability | New vocabularies check for DBpedia in Spanish took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.32533740997314453s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.5459203720092773s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.5529031753540039s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.0017449855804443s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.030200958251953125s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.028060436248779297s
Consistency | Disjoint class check for DBpedia in Spanish took 0.36707186698913574s
Consistency | Check Misplaced properties for DBpedia in Spanish took 7.91673469543457s
Consistency | Misplaced classes for DBpedia in Spanish took 1.142519235610962s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.2199339866638184s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.167708158493042s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 12.874908924102783s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.033089637756347656s
Security | Sign check for DBpedia in Spanish took 0.4690830707550049s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 13.794959545135498s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.7139122486114502s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.021329641342163086s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00010704994201660156s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 9.298324584960938e-06s
INFO | --- Analysis for dbpedia-es took 8063.856875658035s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.120938777923584s
Availability | VoID file availability check for DBpedia in Basque took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.2711052894592285s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.021004199981689453s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.314018249511719e-05s
Believability | Calculation of trust value for DBpedia in Basque took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-eu took 6.497403383255005s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.13511919975280762s
Availability | VoID file availability check for DBpedia in French took 0.0004889965057373047s
Extra | Recovery of all triples for DBpedia in French took 82.24338793754578s
Performance | Total latancy measurement for DBpedia in French took 0.3690962791442871s
Amount of data | Number of triples check for DBpedia in French took 1.5898017883300781s
Interoperability | New terms check for DBpedia in French took 1.8731427192687988s
Versatility | Languages check for DBpedia in French took 300.08372712135315s
Interpretability | Number of blank nodes check for DBpedia in French took 0.20519518852233887s
Security | Check HTTPS for DBpedia in French took 0.17384099960327148s
Interpretability | RDF structures check for DBpedia in French took 0.5305030345916748s
Versatility | Serialization formats check for DBpedia in French took 0.4194982051849365s
Availability | RDF dump link check for DBpedia in French took 5.972752094268799s
License | MR license check for DBpedia in French took 1.2872521877288818s
License | HR license check for DBpedia in French took 70.66909432411194s
Amount of data | Number of property check for DBpedia in French took 0.09891629219055176s
Understandability | Number of label check for DBpedia in French took 1.4263336658477783s
Understandability | URI regex check for DBpedia in French took 0.3192272186279297s
Understandability | Vocabs check for DBpedia in French took 0.1661698818206787s
Verifiability | Authors check for DBpedia in French took 0.2150874137878418s
Verifiability | Publishers check for DBpedia in French took 0.13355350494384766s
Performance | Throughput check for DBpedia in French took 10.306739091873169s
Amount of data | Check the number of entities for DBpedia in French took 2.0304996967315674s
Verifiability | Contribs. check for DBpedia in French took 0.1230926513671875s
Interlinking | sameAs chians check for DBpedia in French took 0.3996701240539551s
Interlinking | skos check for DBpedia in French took 0.1988821029663086s
Interlinking | skos check for DBpedia in French took 0.08169174194335938s
Timeliness | dataset update frequency check for DBpedia in French took 0.4361395835876465s
Currency | Creation date check for DBpedia in French took 0.24781513214111328s
Currency | Modification date check for DBpedia in French took 0.1878809928894043s
Rep.Conc. | URIs length for DBpedia in French took 37.820539474487305s
Interoperability | New vocabularies check for DBpedia in French took 854.2695879936218s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.11953067779541016s
Accuracy | Check Functional Property for DBpedia in French took 0.11979222297668457s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.1285722255706787s
Accuracy | Check Empty annotation labels for DBpedia in French took 25.026012659072876s
Accuracy | Check White space in annotation for DBpedia in French took 3.0043671131134033s
Accuracy | Check Datatype consistency for DBpedia in French took 2.61436128616333s
Consistency | Disjoint class check for DBpedia in French took 0.1613447666168213s
Consistency | Check Misplaced properties for DBpedia in French took 6.911175012588501s
Consistency | Misplaced classes for DBpedia in French took 9.020489931106567s
Consistency | Check Ontology hijacking for DBpedia in French took 21.242436408996582s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.2799248695373535s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 7.083159923553467s
Conciseness | Check Extensional conciseness for DBpedia in French took 2.9791953563690186s
Conciseness | Check Intensional conciseness for DBpedia in French took 2.013444185256958s
Security | Sign check for DBpedia in French took 0.1182253360748291s
Availability | Check URIs Dereferenciability for DBpedia in French took 807.6279802322388s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.4488790035247803s
Reputation | Calculation of the PageRank for DBpedia in French took 0.022220134735107422s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.0002288818359375s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 434.4043893814087s
Believability | Calculation of trust value for DBpedia in French took 5.841255187988281e-05s
INFO | --- Analysis for dbpedia-fr took 2902.6853346824646s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.8686060905456543s
Availability | VoID file availability check for DBpedia in Japanese took 3.991443634033203s
Extra | Recovery of all triples for DBpedia in Japanese took 5.473598003387451s
Performance | Total latancy measurement for DBpedia in Japanese took 6.52871298789978s
Amount of data | Number of triples check for DBpedia in Japanese took 28.474496364593506s
Interoperability | New terms check for DBpedia in Japanese took 18.094294786453247s
Versatility | Languages check for DBpedia in Japanese took 1.3050100803375244s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3074851036071777s
Security | Check HTTPS for DBpedia in Japanese took 0.7878134250640869s
Interpretability | RDF structures check for DBpedia in Japanese took 1.3579297065734863s
Versatility | Serialization formats check for DBpedia in Japanese took 1.3294682502746582s
Availability | RDF dump link check for DBpedia in Japanese took 1.3095030784606934s
License | MR license check for DBpedia in Japanese took 1.3455839157104492s
License | HR license check for DBpedia in Japanese took 61.30619955062866s
Amount of data | Number of property check for DBpedia in Japanese took 1.3023874759674072s
Understandability | Number of label check for DBpedia in Japanese took 1.302361249923706s
Understandability | URI regex check for DBpedia in Japanese took 2.602809429168701s
Understandability | Vocabs check for DBpedia in Japanese took 1.301630973815918s
Verifiability | Authors check for DBpedia in Japanese took 1.3011717796325684s
Verifiability | Publishers check for DBpedia in Japanese took 1.3018951416015625s
Amount of data | Check the number of entities for DBpedia in Japanese took 0.00015425682067871094s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3408691883087158s
Interlinking | sameAs chians check for DBpedia in Japanese took 2.8890180587768555s
Interlinking | skos check for DBpedia in Japanese took 1.313777208328247s
Interlinking | skos check for DBpedia in Japanese took 1.3110456466674805s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.325028419494629s
Currency | Creation date check for DBpedia in Japanese took 2.6244494915008545s
Currency | Modification date check for DBpedia in Japanese took 2.6194088459014893s
Rep.Conc. | URIs length for DBpedia in Japanese took 110.70556092262268s
Interoperability | New vocabularies check for DBpedia in Japanese took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3066656589508057s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.3225843906402588s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.3243827819824219s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 2.97733736038208s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.024984121322631836s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.02837204933166504s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4728283882141113s
Consistency | Check Misplaced properties for DBpedia in Japanese took 94.20089077949524s
Consistency | Misplaced classes for DBpedia in Japanese took 2.9447622299194336s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.201587438583374s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.309328317642212s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 62.63575100898743s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.0339510440826416s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 34.60228371620178s
Security | Sign check for DBpedia in Japanese took 1.373189926147461s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 11.462682008743286s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.3051447868347168s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.02111220359802246s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010538101196289062s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 7.152557373046875e-07s
Believability | Calculation of trust value for DBpedia in Japanese took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia-ja took 990.30140209198s
Availability | SPARQL endpoint availability check for dbpedia lite took 8.463859558105469e-05s
Availability | VoID file availability check for dbpedia lite took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.27912425994873047s
Reputation | Calculation of the PageRank for dbpedia lite took 0.02091836929321289s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00010538101196289062s
Believability | Calculation of trust value for dbpedia lite took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-lite took 11.264235973358154s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.21651339530944824s
Availability | VoID file availability check for DBpedia in Dutch took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.26792025566101074s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.021007776260375977s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00016450881958007812s
Believability | Calculation of trust value for DBpedia in Dutch took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-nl took 3.1863961219787598s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 20.785972118377686s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.31871891021728516s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.02088332176208496s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 7.915496826171875e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 1.0728836059570312e-05s
INFO | --- Analysis for dbpedia-pt took 31.648964881896973s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 8.606910705566406e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.2679152488708496s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.02077507972717285s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.508827209472656e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.0013580322265625e-05s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 13.943352460861206s
Availability | SPARQL endpoint availability check for DBTropes took 8.511543273925781e-05s
Availability | VoID file availability check for DBTropes took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for DBTropes took 0.2706749439239502s
Reputation | Calculation of the PageRank for DBTropes took 0.0209810733795166s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for DBTropes took 8.893013000488281e-05s
Believability | Calculation of trust value for DBTropes took 9.775161743164062e-06s
INFO | --- Analysis for dbtropes took 3.45259165763855s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.220008850097656e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.26645612716674805s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.023473262786865234s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.2928924560546875e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 1.2159347534179688e-05s
INFO | --- Analysis for dbtune-artists-last-fm took 2.6568663120269775s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 8.726119995117188e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.26885008811950684s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.02271413803100586s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.075599670410156e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.2874603271484375e-05s
INFO | --- Analysis for dbtune-audioscrobbler took 2.598327398300171s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.521219730377197s
Availability | VoID file availability check for DBTune.org/classical took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.2674884796142578s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.022153139114379883s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.52587890625e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0011179447174072266s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 9.870529174804688e-05s
Believability | Calculation of trust value for DBTune.org/classical took 7.62939453125e-06s
INFO | --- Analysis for dbtune-classical took 8.759899139404297s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.681314945220947s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.2820720672607422s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020596981048583984s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.985664367675781e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 1.1205673217773438e-05s
INFO | --- Analysis for dbtune-john-peel-sessions took 10.916659355163574s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 5.499515771865845s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.267075777053833s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.02046513557434082s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.771087646484375e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.1444091796875e-05s
INFO | --- Analysis for dbtune-magnatune took 9.392406940460205s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 180.43022394180298s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.2996087074279785s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.020791053771972656s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00011205673217773438s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 5.4836273193359375e-06s
INFO | --- Analysis for dbtune-musicbrainz took 433.4584131240845s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.29764747619628906s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.27422022819519043s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.021327495574951172s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 6.341934204101562e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 9.5367431640625e-06s
INFO | --- Analysis for dbtune-myspace took 2.989872694015503s
Availability | SPARQL endpoint availability check for data.dcs took 8.368492126464844e-05s
Availability | VoID file availability check for data.dcs took 0.0004184246063232422s
Completeness | Calculation of interlinking completeness for data.dcs took 0.2629837989807129s
Reputation | Calculation of the PageRank for data.dcs took 0.02131032943725586s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.771087646484375e-05s
Believability | Calculation of trust value for data.dcs took 9.059906005859375e-06s
INFO | --- Analysis for dcs-sheffield took 2.490493059158325s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 8.511543273925781e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.26433777809143066s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.021121501922607422s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 4.00543212890625e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 1.0728836059570312e-05s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.385708808898926s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 8.678436279296875e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.2651252746582031s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.021097660064697266s
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.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.506111145019531e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.0251998901367188e-05s
INFO | --- Analysis for debian-package-tracking-system took 4.472051620483398s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.410743713378906e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.2667815685272217s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.021280288696289062s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.528594970703125e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.2159347534179688e-05s
INFO | --- Analysis for desaparecidos took 2.853861093521118s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 8.893013000488281e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.2722611427307129s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.02108168601989746s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.00010061264038085938s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.049041748046875e-05s
INFO | --- Analysis for deustoentrepreneurship took 5.177659511566162s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 8.7738037109375e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0007646083831787109s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.27002501487731934s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.02120232582092285s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.0001068115234375s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.239776611328125e-05s
INFO | --- Analysis for deustotech took 5.064099073410034s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.3412389755249023s
Availability | VoID file availability check for Deutsche Biographie took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.26879143714904785s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.021959543228149414s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.8623809814453125e-05s
Believability | Calculation of trust value for Deutsche Biographie took 9.5367431640625e-06s
INFO | --- Analysis for deutsche-biographie took 4.165269613265991s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 9.1552734375e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2692408561706543s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.021793842315673828s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.555152893066406e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 9.775161743164062e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 5.9308483600616455s
Availability | SPARQL endpoint availability check for dev8d took 8.440017700195312e-05s
Availability | VoID file availability check for dev8d took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for dev8d took 0.27838921546936035s
Reputation | Calculation of the PageRank for dev8d took 0.020923614501953125s
Interlinking | Calculation of Degree of Connection for dev8d took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.794929504394531e-05s
Believability | Calculation of trust value for dev8d took 1.0013580322265625e-05s
INFO | --- Analysis for dev8d took 3.532017707824707s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.244865894317627s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.28212547302246094s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.021303176879882812s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.8650970458984375e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.1444091796875e-05s
INFO | --- Analysis for dewey_decimal_classification took 93.12002372741699s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 8.58306884765625e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.2727644443511963s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.02088165283203125s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.0040740966796875e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 1.1682510375976562e-05s
INFO | --- Analysis for DHSVM took 21.193373441696167s
Availability | SPARQL endpoint availability check for Diavgeia took 8.702278137207031e-05s
Availability | VoID file availability check for Diavgeia took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.26919102668762207s
Reputation | Calculation of the PageRank for Diavgeia took 0.020788192749023438s
Interlinking | Calculation of Degree of Connection for Diavgeia took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.034706115722656e-05s
Believability | Calculation of trust value for Diavgeia took 7.152557373046875e-06s
INFO | --- Analysis for diavgeia took 5.347222566604614s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 9.059906005859375e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.2942674160003662s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02065563201904297s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011372566223144531s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.1444091796875e-05s
INFO | --- Analysis for didactalia took 8.42034387588501s
Availability | SPARQL endpoint availability check for DisGeNET took 1.6958587169647217s
Availability | VoID file availability check for DisGeNET took 0.00067138671875s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.27561378479003906s
Reputation | Calculation of the PageRank for DisGeNET took 0.02062201499938965s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015807151794433594s
Believability | Calculation of trust value for DisGeNET took 1.2159347534179688e-05s
INFO | --- Analysis for disgenet took 7.31009316444397s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 9.131431579589844e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.28348588943481445s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.0209195613861084s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.123283386230469e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.1920928955078125e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 5.795301198959351s
Availability | SPARQL endpoint availability check for DM2E took 8.654594421386719e-05s
Availability | VoID file availability check for DM2E took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for DM2E took 0.2633209228515625s
Reputation | Calculation of the PageRank for DM2E took 0.022650718688964844s
Interlinking | Calculation of Degree of Connection for DM2E took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00010728836059570312s
Believability | Calculation of trust value for DM2E took 1.1444091796875e-05s
INFO | --- Analysis for dm2e took 3.345324754714966s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 5.4836273193359375e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0012936592102050781s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.31516480445861816s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.02080821990966797s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00015306472778320312s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 1.0013580322265625e-05s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 7.026660203933716s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.458427429199219e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0006773471832275391s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.2700371742248535s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020926237106323242s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 5.984306335449219e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 9.5367431640625e-06s
INFO | --- Analysis for doi took 7.034994840621948s
Availability | SPARQL endpoint availability check for Driggu Florentino took 9.083747863769531e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.26480579376220703s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.021084070205688477s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 2.8848648071289062e-05s
Believability | Calculation of trust value for Driggu Florentino took 1.2159347534179688e-05s
INFO | --- Analysis for Driggu took 3.2758302688598633s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 1.1348841190338135s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.2961461544036865s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.5762786865234375e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.2159347534179688e-05s
INFO | --- Analysis for drug-data-hifm took 15.904482126235962s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.79949712753296s
Availability | VoID file availability check for MetaLex Document Server took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.2696797847747803s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.021076440811157227s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.647804260253906e-05s
Believability | Calculation of trust value for MetaLex Document Server took 1.239776611328125e-05s
INFO | --- Analysis for dutch-national-regulations-metalex took 555.1240842342377s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.31133770942688s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.2775142192840576s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020869970321655273s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0008018016815185547s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.100799560546875e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 1.0967254638671875e-05s
INFO | --- Analysis for dutch-ships-and-sailors took 13.635509967803955s
Availability | SPARQL endpoint availability check for DWS-Group took 8.630752563476562e-05s
Availability | VoID file availability check for DWS-Group took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.263995885848999s
Reputation | Calculation of the PageRank for DWS-Group took 0.02344369888305664s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010514259338378906s
Believability | Calculation of trust value for DWS-Group took 1.1444091796875e-05s
INFO | --- Analysis for dws-group took 2.5269267559051514s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 8.58306884765625e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.3235151767730713s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.021258115768432617s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 2.86102294921875e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.1205673217773438e-05s
INFO | --- Analysis for E1 took 3.926070213317871s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.06315755844116211s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.2629683017730713s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00010919570922851562s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i-alaska took 2.5056939125061035s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.023826122283935547s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004119873046875s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.2630317211151123s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.022822141647338867s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.459785461425781e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-cau took 2.5004122257232666s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.025844335556030273s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.26311278343200684s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.02270984649658203s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.270408630371094e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.5065231323242188s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.030585765838623047s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.2621281147003174s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.107589721679688e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-cdrewu took 2.471139669418335s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.050634145736694336s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.26171302795410156s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.022954463958740234s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.0001289844512939453s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 9.5367431640625e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.4801979064941406s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0312044620513916s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.2597463130950928s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.296966552734375e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-famu took 2.505866289138794s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.024202346801757812s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.274247407913208s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.021538496017456055s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00012159347534179688s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-harvard took 2.5387566089630127s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.03243446350097656s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.2619132995605469s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.022611379623413086s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00011801719665527344s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-hawaii took 2.493032455444336s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.03170299530029297s
Availability | VoID file availability check for eagle-i @ Howard University took 0.00040650367736816406s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.2704887390136719s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.02240133285522461s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.461143493652344e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-howard took 2.5051183700561523s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.036145687103271484s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0004038810729980469s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.2618546485900879s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.02082204818725586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.557868957519531e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.5103683471679688s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.044162750244140625s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.29087257385253906s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.02221202850341797s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0011434555053710938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.0001404285430908203s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-jsu took 2.5505356788635254s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.054193973541259766s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.29848742485046387s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.020811796188354492s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.600120544433594e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-meharry took 2.52030611038208s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.03161954879760742s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.27379631996154785s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.250640869140625e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-montana took 2.480747938156128s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.03153562545776367s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.268143892288208s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020686626434326172s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.489059448242188e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 9.059906005859375e-06s
INFO | --- Analysis for eagle-i-msm took 2.4662275314331055s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.03234553337097168s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2656247615814209s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.020821571350097656s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00012302398681640625s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-ohsu took 2.493131637573242s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.025383710861206055s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.27126264572143555s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020276308059692383s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.103515625e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-psm took 2.466776132583618s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.02290487289428711s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.2938249111175537s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.008148193359375e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-tsu took 2.5095958709716797s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.030414342880249023s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0004222393035888672s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2658274173736572s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020534753799438477s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 5.8650970458984375e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i-tuskegee took 2.486513614654541s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.044651031494140625s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.275759220123291s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.021032094955444336s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00010228157043457031s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.533695697784424s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0244901180267334s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.2627110481262207s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.020941495895385742s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00012755393981933594s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-upr took 2.478146553039551s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.023894309997558594s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0004162788391113281s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.27177000045776367s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 5.7697296142578125e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.0013580322265625e-05s
INFO | --- Analysis for eagle-i-utep took 2.4794363975524902s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.030389785766601562s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.00042319297790527344s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.2679932117462158s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.02072930335998535s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.104873657226562e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-utsa took 2.4898972511291504s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.16078734397888184s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0004227161407470703s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.26227736473083496s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.022451162338256836s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 8.606910705566406e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.0013580322265625e-05s
INFO | --- Analysis for eagle-i-vanderbilt took 2.6330254077911377s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.03159213066101074s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.27188920974731445s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020746469497680664s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.033348083496094e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-xula took 2.484114646911621s
Availability | SPARQL endpoint availability check for Emergency situation took 0.5375173091888428s
Availability | VoID file availability check for Emergency situation took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.2706475257873535s
Reputation | Calculation of the PageRank for Emergency situation took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.696846008300781e-05s
Believability | Calculation of trust value for Emergency situation took 1.0967254638671875e-05s
INFO | --- Analysis for Earthquake took 3.6598575115203857s
Availability | SPARQL endpoint availability check for ESO took 0.5463602542877197s
Availability | VoID file availability check for ESO took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for ESO took 0.26982593536376953s
Reputation | Calculation of the PageRank for ESO took 0.022872447967529297s
Interlinking | Calculation of Degree of Connection for ESO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for ESO took 7.963180541992188e-05s
Believability | Calculation of trust value for ESO took 1.0967254638671875e-05s
INFO | --- Analysis for Earthquake_case took 3.877300500869751s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.09531903266906738s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.2693207263946533s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.02048516273498535s
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.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 9.965896606445312e-05s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for ecb-linked-data took 2.572497844696045s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 5.8287599086761475s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.26971006393432617s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.021413087844848633s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.600120544433594e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 8.821487426757812e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 13.885721683502197s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.471071720123291s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.2714705467224121s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.022432327270507812s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0008318424224853516s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 7.772445678710938e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for ecco-tcp-linked-data took 6.438557147979736s
Availability | SPARQL endpoint availability check for ECLAP took 20.84902834892273s
Availability | VoID file availability check for ECLAP took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for ECLAP took 0.26456642150878906s
Reputation | Calculation of the PageRank for ECLAP took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.409385681152344e-05s
Believability | Calculation of trust value for ECLAP took 1.2159347534179688e-05s
INFO | --- Analysis for eclap took 53.30855584144592s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 8.96453857421875e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.2611849308013916s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.02277088165283203s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.33514404296875e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.0251998901367188e-05s
INFO | --- Analysis for ECNU-GISer took 4.070152997970581s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.1961669921875e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.26554083824157715s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.022701501846313477s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.364418029785156e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 9.775161743164062e-06s
INFO | --- Analysis for ecs took 2.5123934745788574s
Availability | SPARQL endpoint availability check for Edublogs took 8.535385131835938e-05s
Availability | VoID file availability check for Edublogs took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Edublogs took 0.276324987411499s
Reputation | Calculation of the PageRank for Edublogs took 0.02079629898071289s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.751319885253906e-05s
Believability | Calculation of trust value for Edublogs took 7.62939453125e-06s
INFO | --- Analysis for edublogs took 3.2792985439300537s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.4482102394104004s
Availability | VoID file availability check for education.data.gov.uk took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.26476359367370605s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.369850158691406e-05s
Believability | Calculation of trust value for education.data.gov.uk took 8.58306884765625e-06s
INFO | --- Analysis for education-data-gov-uk took 4.441663503646851s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 391.5018963813782s
Availability | VoID file availability check for Educational programs - SISVU took 0.0008716583251953125s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.6205887794494629s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.023318052291870117s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 6.771087646484375e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.2159347534179688e-05s
INFO | --- Analysis for educationalprograms_sisvu took 1319.7658157348633s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 1.0282461643218994s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.2770817279815674s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.02269458770751953s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.600120544433594e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 7.867813110351562e-06s
INFO | --- Analysis for eea took 8.914963960647583s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.4539198875427246s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.2712132930755615s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020954132080078125s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.1975250244140625e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 8.58306884765625e-06s
INFO | --- Analysis for eea-rod took 5.074423551559448s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.1580049991607666s
Availability | VoID file availability check for EEA Vocabularies took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.2633821964263916s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.02103710174560547s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 7.867813110351562e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.1682510375976562e-05s
INFO | --- Analysis for eea-vocabularies took 4.803229093551636s
Availability | SPARQL endpoint availability check for E-Government Ontology took 1.742821216583252s
Availability | VoID file availability check for E-Government Ontology took 0.0003464221954345703s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.2644820213317871s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.023033857345581055s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 4.482269287109375e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for EGovOntology took 5.204500675201416s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5352997779846191s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0005571842193603516s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 2.5823686122894287s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1606340408325195s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6224431991577148s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.7754127979278564s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.33062410354614s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.00366473197937s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7135214805603027s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8520886898040771s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24947571754455566s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6260673999786377s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 6.816296815872192s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2344970703125s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5020108222961426s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6539545059204102s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3252873420715332s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.406635046005249s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24135637283325195s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 11.580106496810913s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 6.961822509765625e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3820621967315674s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.29656314849853516s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5541043281555176s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.22900176048278809s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3894026279449463s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9242472648620605s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24774861335754395s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.662423849105835s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.22857451438903809s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3450460433959961s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.35686802864074707s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3976771831512451s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.029806852340698242s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.028200864791870117s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23390603065490723s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.109179258346558s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.43335461616516113s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.1954474449157715s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.159816026687622s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.822419881820679s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.033705949783325195s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.37447237968444824s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5610074996948242s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 2944.1693861484528s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.45883679389953613s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.021540403366088867s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.9604644775390625e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.6689300537109375e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 1.239776611328125e-05s
INFO | --- Analysis for ei2a took 3173.28218126297s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 5.078315734863281e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.2680020332336426s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.020263671875s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010347366333007812s
Believability | Calculation of trust value for EIONET RDF Data took 8.106231689453125e-06s
INFO | --- Analysis for eionet-rdf took 2.9850425720214844s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.2438507080078125e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.2637622356414795s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 2.7894973754882812e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 1.5497207641601562e-05s
INFO | --- Analysis for ElgooG_ took 2.383474349975586s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.15513563156128s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.25919532775878906s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 6.890296936035156e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 6.9141387939453125e-06s
INFO | --- Analysis for elviajero took 21.894874095916748s
Availability | SPARQL endpoint availability check for EMN took 0.00010085105895996094s
Availability | VoID file availability check for EMN took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for EMN took 0.256089448928833s
Reputation | Calculation of the PageRank for EMN took 0.02074742317199707s
Interlinking | Calculation of Degree of Connection for EMN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EMN took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for EMN took 3.838539123535156e-05s
Believability | Calculation of trust value for EMN took 7.152557373046875e-06s
INFO | --- Analysis for emn took 2.6011300086975098s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.27495527267456055s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020860910415649414s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.054473876953125e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 4.5299530029296875e-06s
INFO | --- Analysis for enakting-co2emission took 2.411266803741455s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 5.030632019042969e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.2646331787109375s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 3.814697265625e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 4.291534423828125e-06s
INFO | --- Analysis for enakting-crime took 2.4345312118530273s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.506111145019531e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.2649717330932617s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.020688772201538086s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.363059997558594e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 8.58306884765625e-06s
INFO | --- Analysis for enakting-energy took 2.453948736190796s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.26566386222839355s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.012222290039062e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 4.291534423828125e-06s
INFO | --- Analysis for enakting-mortality took 2.4168949127197266s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0002110004425048828s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.26824522018432617s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.02135777473449707s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.647804260253906e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 8.344650268554688e-06s
INFO | --- Analysis for enakting-nhs took 2.423729181289673s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 8.749961853027344e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.260408878326416s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.316734313964844e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 8.344650268554688e-06s
INFO | --- Analysis for enakting-population took 2.458282709121704s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.5677752494812012s
Availability | VoID file availability check for English Heritage Periods List took 0.0007116794586181641s
Extra | Recovery of all triples for English Heritage Periods List took 0.3234138488769531s
Performance | Total latancy measurement for English Heritage Periods List took 1.3808560371398926s
Amount of data | Number of triples check for English Heritage Periods List took 0.43656253814697266s
Versatility | Languages check for English Heritage Periods List took 0.2495863437652588s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.4682796001434326s
Security | Check HTTPS for English Heritage Periods List took 0.18982911109924316s
Interpretability | RDF structures check for English Heritage Periods List took 0.24208498001098633s
Versatility | Serialization formats check for English Heritage Periods List took 0.4180166721343994s
Availability | RDF dump link check for English Heritage Periods List took 0.3107917308807373s
License | MR license check for English Heritage Periods List took 0.4440183639526367s
License | HR license check for English Heritage Periods List took 0.32018280029296875s
Amount of data | Number of property check for English Heritage Periods List took 0.3259737491607666s
Understandability | Number of label check for English Heritage Periods List took 0.4232609272003174s
Understandability | URI regex check for English Heritage Periods List took 0.5976972579956055s
Understandability | Vocabs check for English Heritage Periods List took 0.468677282333374s
Verifiability | Authors check for English Heritage Periods List took 0.5117981433868408s
Verifiability | Publishers check for English Heritage Periods List took 0.3744392395019531s
Performance | Throughput check for English Heritage Periods List took 11.330657243728638s
Amount of data | Check the number of entities for English Heritage Periods List took 7.081031799316406e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.33658552169799805s
Interlinking | sameAs chians check for English Heritage Periods List took 0.30815696716308594s
Interlinking | skos check for English Heritage Periods List took 0.3043520450592041s
Interlinking | skos check for English Heritage Periods List took 0.3313922882080078s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.4159705638885498s
Currency | Creation date check for English Heritage Periods List took 0.6507787704467773s
Currency | Modification date check for English Heritage Periods List took 0.676645040512085s
Rep.Conc. | URIs length for English Heritage Periods List took 0.6036741733551025s
Interoperability | New vocabularies check for English Heritage Periods List took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.39502906799316406s
Accuracy | Check Functional Property for English Heritage Periods List took 0.2959475517272949s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.3299565315246582s
Consistency | Disjoint class check for English Heritage Periods List took 0.2968556880950928s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.32890772819519043s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.491473913192749s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00015735626220703125s
Security | Sign check for English Heritage Periods List took 0.3360021114349365s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.27064037322998047s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.504753112792969e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Periods List took 1.2159347534179688e-05s
INFO | --- Analysis for english-heritage-periods-list took 52.06235957145691s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.311737060546875s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0005552768707275391s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 1.4733541011810303s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 0.8490347862243652s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.2802083492279053s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.4278619289398193s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.4676930904388428s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 30.45256495475769s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.16455531120300293s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.3109316825866699s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.127577543258667s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 43.68108296394348s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.29284071922302246s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.767337322235107s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.13414812088012695s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.2313520908355713s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.30738282203674316s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.47888922691345215s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.12230181694030762s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.21814608573913574s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 12.216284990310669s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 8.511543273925781e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.12136292457580566s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.28677821159362793s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.2263951301574707s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.12067484855651855s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.8055765628814697s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.8083510398864746s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.23328447341918945s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 3.6790761947631836s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.16346311569213867s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.14807415008544922s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.14470911026000977s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.38344669342041016s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 0.8247501850128174s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 3.687528610229492s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.3535833358764648s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.00016260147094726562s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 1.197068691253662s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.2134535312652588s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.5555942058563232s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.020993709564208984s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 6.413459777832031e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 4.76837158203125e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 267.3499348163605s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.18915343284606934s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.00042819976806640625s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 1.0003654956817627s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 1.0444509983062744s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.18418407440185547s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.3672325611114502s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.4034411907196045s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 30.22194004058838s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.10178279876708984s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.1891615390777588s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.18924975395202637s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 42.06679606437683s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.19247984886169434s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.139019012451172s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.12839317321777344s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.1239314079284668s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.3038961887359619s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.39831995964050293s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.196242094039917s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.12193655967712402s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 12.938720226287842s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 7.271766662597656e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.119384765625s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.18541669845581055s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.19309163093566895s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.1822659969329834s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.1856074333190918s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.38645267486572266s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.1323840618133545s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.5777130126953125s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.1202394962310791s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.821993350982666s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.1986384391784668s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.12736153602600098s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.3365952968597412s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 1.1780073642730713s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.3763041496276855s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.00015091896057128906s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.2231428623199463s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.12244367599487305s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.26966404914855957s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.02090620994567871s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 4.673004150390625e-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.298324584960938e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 251.1619074344635s
Availability | SPARQL endpoint availability check for English WordNet took 0.00011396408081054688s
Availability | VoID file availability check for English WordNet took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for English WordNet took 0.2650742530822754s
Reputation | Calculation of the PageRank for English WordNet took 0.020932912826538086s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.3855438232421875e-05s
Believability | Calculation of trust value for English WordNet took 1.0967254638671875e-05s
INFO | --- Analysis for english-wordnet took 3.0944299697875977s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 5.07675576210022s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0004210472106933594s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.269977331161499s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.021212100982666016s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 8.654594421386719e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.3589859008789062e-05s
INFO | --- Analysis for enipedia took 7.50212836265564s
Availability | SPARQL endpoint availability check for Enslaved.org took 8.535385131835938e-05s
Availability | VoID file availability check for Enslaved.org took 0.0010585784912109375s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.33714962005615234s
Reputation | Calculation of the PageRank for Enslaved.org took 0.02067732810974121s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.170967102050781e-05s
Believability | Calculation of trust value for Enslaved.org took 1.1205673217773438e-05s
INFO | --- Analysis for enslaved.org took 4.6017279624938965s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.25650811195373535s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.27344465255737305s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.02188897132873535s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.054473876953125e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 1.0967254638671875e-05s
INFO | --- Analysis for entice-graph took 2.869638442993164s
Availability | SPARQL endpoint availability check for Entrez Gene took 9.036064147949219e-05s
Availability | VoID file availability check for Entrez Gene took 0.0007810592651367188s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.26618480682373047s
Reputation | Calculation of the PageRank for Entrez Gene took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 6.127357482910156e-05s
Believability | Calculation of trust value for Entrez Gene took 1.0967254638671875e-05s
INFO | --- Analysis for entrez_gene took 27.012706995010376s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 0.92010498046875s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.270709753036499s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.02088308334350586s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 4.887580871582031e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 8.821487426757812e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 10.80564284324646s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.25119638442993164s
Availability | VoID file availability check for environment.data.gov.uk took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.2625460624694824s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.02192068099975586s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.5299530029296875e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 8.58306884765625e-06s
INFO | --- Analysis for environment-data-gov-uk took 8.597124099731445s
Availability | SPARQL endpoint availability check for EARTh took 272.3030815124512s
Availability | VoID file availability check for EARTh took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for EARTh took 0.2611870765686035s
Reputation | Calculation of the PageRank for EARTh took 0.021210670471191406s
Interlinking | Calculation of Degree of Connection for EARTh took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for EARTh took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00010371208190917969s
Believability | Calculation of trust value for EARTh took 1.049041748046875e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 563.8505651950836s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.45705318450927734s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0004909038543701172s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 99.75085377693176s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.87796950340271s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 9.525504112243652s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 14.09065842628479s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.17183685302734s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.127239942550659s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.24251961708068848s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 10.19327712059021s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.21898961067199707s
License | MR license check for Micka (EO metadata) @PSNC took 0.3768191337585449s
License | HR license check for Micka (EO metadata) @PSNC took 300.21881890296936s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.17955732345581055s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 1.8232338428497314s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 0.5878129005432129s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.33650946617126465s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.17404937744140625s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.2328953742980957s
Performance | Throughput check for Micka (EO metadata) @PSNC took 10.705202579498291s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 5.0067901611328125e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.18816113471984863s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.18187904357910156s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4741702079772949s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4527621269226074s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 4.5523905754089355s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.4533975124359131s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.23192358016967773s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 152.37577724456787s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.1793220043182373s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.32103610038757324s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.3086659908294678s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 43.895628213882446s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.6180505752563477s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.61769700050354s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.17397022247314453s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 86.96423149108887s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.255985736846924s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 29.122546911239624s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.2552824020385742s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 87.24695420265198s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.6644914150238037s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.539370059967041s
Security | Sign check for Micka (EO metadata) @PSNC took 0.7958025932312012s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 9.022828578948975s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.4377133846282959s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.022037029266357422s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 4.172325134277344e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 1.1205673217773438e-05s
INFO | --- Analysis for EO_metadata took 2217.4354960918427s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 9.012222290039062e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.26488780975341797s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.02086949348449707s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 2.8133392333984375e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 1.0967254638671875e-05s
INFO | --- Analysis for EOKP-Datasets took 3.083216428756714s
Availability | SPARQL endpoint availability check for EPA-CDR took 0.0002651214599609375s
Availability | VoID file availability check for EPA-CDR took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.2651832103729248s
Reputation | Calculation of the PageRank for EPA-CDR took 0.022115230560302734s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.5762786865234375e-05s
Believability | Calculation of trust value for EPA-CDR took 1.0728836059570312e-05s
INFO | --- Analysis for epa-cdr took 6.498457431793213s
Availability | SPARQL endpoint availability check for EPA-FRS took 8.58306884765625e-05s
Availability | VoID file availability check for EPA-FRS took 0.0010111331939697266s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.2638554573059082s
Reputation | Calculation of the PageRank for EPA-FRS took 0.02101731300354004s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.200241088867188e-05s
Believability | Calculation of trust value for EPA-FRS took 9.298324584960938e-06s
INFO | --- Analysis for epa-frs took 5.639265775680542s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.601478576660156e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.26620936393737793s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.022462844848632812s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.52587890625e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.266334533691406e-05s
Believability | Calculation of trust value for EPA-RCRA took 9.298324584960938e-06s
INFO | --- Analysis for epa-rcra took 5.6750030517578125s
Availability | SPARQL endpoint availability check for EPA-SRS took 8.511543273925781e-05s
Availability | VoID file availability check for EPA-SRS took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.2619478702545166s
Reputation | Calculation of the PageRank for EPA-SRS took 0.02076864242553711s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.462501525878906e-05s
Believability | Calculation of trust value for EPA-SRS took 8.106231689453125e-06s
INFO | --- Analysis for epa-srs took 5.648762226104736s
Availability | SPARQL endpoint availability check for EPA-TRI took 8.559226989746094e-05s
Availability | VoID file availability check for EPA-TRI took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.27214527130126953s
Reputation | Calculation of the PageRank for EPA-TRI took 0.021033763885498047s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.314018249511719e-05s
Believability | Calculation of trust value for EPA-TRI took 8.344650268554688e-06s
INFO | --- Analysis for epa-tri took 5.638700008392334s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.027652263641357422s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0004096031188964844s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.2719452381134033s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.02091193199157715s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.0001575946807861328s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.499504327774048s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.355884313583374s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.272965669631958s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.02329850196838379s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0011692047119140625s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 0.00010251998901367188s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 1.4066696166992188e-05s
INFO | --- Analysis for eprtr took 3.5263192653656006s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.4237492084503174s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0005893707275390625s
Extra | Recovery of all triples for Railway Infrastructure KG took 61.61945652961731s
Performance | Total latancy measurement for Railway Infrastructure KG took 1.0220434665679932s
Amount of data | Number of triples check for Railway Infrastructure KG took 0.22887301445007324s
Interoperability | New terms check for Railway Infrastructure KG took 1.536435604095459s
Versatility | Languages check for Railway Infrastructure KG took 86.79337954521179s
Interpretability | Number of blank nodes check for Railway Infrastructure KG took 0.2530660629272461s
Interpretability | RDF structures check for Railway Infrastructure KG took 0.7288742065429688s
Versatility | Serialization formats check for Railway Infrastructure KG took 0.2546498775482178s
Availability | RDF dump link check for Railway Infrastructure KG took 0.2092440128326416s
License | MR license check for Railway Infrastructure KG took 0.3170511722564697s
License | HR license check for Railway Infrastructure KG took 63.71364116668701s
Amount of data | Number of property check for Railway Infrastructure KG took 0.32016921043395996s
Understandability | Number of label check for Railway Infrastructure KG took 0.5411074161529541s
Understandability | URI regex check for Railway Infrastructure KG took 0.4468879699707031s
Understandability | Vocabs check for Railway Infrastructure KG took 0.21606206893920898s
Verifiability | Authors check for Railway Infrastructure KG took 0.2854487895965576s
Verifiability | Publishers check for Railway Infrastructure KG took 0.20867133140563965s
Performance | Throughput check for Railway Infrastructure KG took 10.561043739318848s
Verifiability | Contribs. check for Railway Infrastructure KG took 0.24686431884765625s
Interlinking | sameAs chians check for Railway Infrastructure KG took 0.20880341529846191s
Interlinking | skos check for Railway Infrastructure KG took 0.23479628562927246s
Interlinking | skos check for Railway Infrastructure KG took 0.23610210418701172s
Timeliness | dataset update frequency check for Railway Infrastructure KG took 0.20779848098754883s
Currency | Creation date check for Railway Infrastructure KG took 0.4448385238647461s
Currency | Modification date check for Railway Infrastructure KG took 0.19945836067199707s
Rep.Conc. | URIs length for Railway Infrastructure KG took 22.491880893707275s
Interoperability | New vocabularies check for Railway Infrastructure KG took 25.65785050392151s
Consistency | Deprecated classes/propertiers check for Railway Infrastructure KG took 0.19889187812805176s
Accuracy | Check Functional Property for Railway Infrastructure KG took 0.26125431060791016s
Accuracy | Check Inverse Functional Property for Railway Infrastructure KG took 0.21886777877807617s
Accuracy | Check Empty annotation labels for Railway Infrastructure KG took 13.975707769393921s
Accuracy | Check White space in annotation for Railway Infrastructure KG took 2.5262691974639893s
Accuracy | Check Datatype consistency for Railway Infrastructure KG took 2.5909388065338135s
Consistency | Disjoint class check for Railway Infrastructure KG took 0.2615842819213867s
Consistency | Check Misplaced properties for Railway Infrastructure KG took 1.641092300415039s
Consistency | Misplaced classes for Railway Infrastructure KG took 8.242425441741943s
Consistency | Check Ontology hijacking for Railway Infrastructure KG took 17.753321647644043s
Consistency | Check Invalid usage of undefined classes for Railway Infrastructure KG took 1.483109951019287s
Consistency | Check Invalid usage of undefined properties for Railway Infrastructure KG took 2.704831600189209s
Conciseness | Check Extensional conciseness for Railway Infrastructure KG took 2.852909803390503s
Conciseness | Check Intensional conciseness for Railway Infrastructure KG took 0.34609079360961914s
Security | Sign check for Railway Infrastructure KG took 0.4634068012237549s
Availability | Check URIs Dereferenciability for Railway Infrastructure KG took 2144.5997829437256s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.7054240703582764s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.022646427154541016s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 2.6464462280273438e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 9.1552734375e-05s
Interoperability | Check the re-using of existing vocabs for Railway Infrastructure KG took 20.539175271987915s
Believability | Calculation of trust value for Railway Infrastructure KG took 8.58306884765625e-06s
INFO | --- Analysis for ERAKG took 2603.7147204875946s
Availability | SPARQL endpoint availability check for reg took 4.553794860839844e-05s
Availability | VoID file availability check for reg took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for reg took 0.2623105049133301s
Reputation | Calculation of the PageRank for reg took 0.02132558822631836s
Interlinking | Calculation of Degree of Connection for reg took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for reg took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for reg took 1.1682510375976562e-05s
Believability | Calculation of trust value for reg took 1.1920928955078125e-05s
INFO | --- Analysis for erg took 2.4554431438446045s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.21786165237426758s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0004138946533203125s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.25708532333374023s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.022075891494750977s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.147125244140625e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 4.76837158203125e-06s
INFO | --- Analysis for es-msssi-drug-prices took 2.892936944961548s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 8.606910705566406e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.2711164951324463s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.021036863327026367s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.702278137207031e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 7.3909759521484375e-06s
INFO | --- Analysis for esd-standards took 4.204123497009277s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 8.559226989746094e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.26892542839050293s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.02119135856628418s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 9.226799011230469e-05s
Believability | Calculation of trust value for ESD-Toolkit took 5.0067901611328125e-06s
INFO | --- Analysis for esd-toolkit took 3.1035304069519043s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.1961669921875e-05s
Availability | VoID file availability check for Dataset Esis took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.25816774368286133s
Reputation | Calculation of the PageRank for Dataset Esis took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 2.7418136596679688e-05s
Believability | Calculation of trust value for Dataset Esis took 6.9141387939453125e-06s
INFO | --- Analysis for esislearning took 2.777069568634033s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 5.1021575927734375e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.2559993267059326s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020526885986328125s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 2.6702880859375e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 5.7220458984375e-06s
INFO | --- Analysis for ESV took 3.369117259979248s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.6402289867401123s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.27112436294555664s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.02085709571838379s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.504753112792969e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 9.775161743164062e-06s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.277440071105957s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 6.162993431091309s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.00067138671875s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.27317237854003906s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.021518230438232422s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0008859634399414062s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 8.320808410644531e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 1.1444091796875e-05s
INFO | --- Analysis for eu-agencies-bodies took 17.125059843063354s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 5.602836608886719e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0006837844848632812s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.2763082981109619s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020812511444091797s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.176399230957031e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 9.5367431640625e-06s
INFO | --- Analysis for eu-institutions took 8.055355787277222s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.133195161819458s
Availability | VoID file availability check for EU Parliament Media Library took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.27429795265197754s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02253556251525879s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 4.076957702636719e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 8.106231689453125e-06s
INFO | --- Analysis for eu-parliament-media took 8.415364503860474s
Availability | SPARQL endpoint availability check for EU Who Is Who took 1.0309102535247803s
Availability | VoID file availability check for EU Who Is Who took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2673990726470947s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020807504653930664s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.5762786865234375e-05s
Believability | Calculation of trust value for EU Who Is Who took 8.106231689453125e-06s
INFO | --- Analysis for eu-who-is-who took 11.476166248321533s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 1.1037530899047852s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.27114152908325195s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.021107196807861328s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.076957702636719e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for eumida-linked-data took 9.817636489868164s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.3286001682281494s
Availability | VoID file availability check for European Nature Information System took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.27391862869262695s
Reputation | Calculation of the PageRank for European Nature Information System took 0.021188735961914062s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010442733764648438s
Believability | Calculation of trust value for European Nature Information System took 1.1682510375976562e-05s
INFO | --- Analysis for eunis took 4.080042839050293s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 5.405146837234497s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0012171268463134766s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.2721567153930664s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020409822463989258s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 6.890296936035156e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 1.1444091796875e-05s
INFO | --- Analysis for eur-lex-rdf took 15.778881788253784s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 0.9519755840301514s
Availability | VoID file availability check for Standard Eurobarometer took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.2630622386932373s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020787715911865234s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.124641418457031e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 8.58306884765625e-06s
INFO | --- Analysis for eurobarometer-standard took 9.7778799533844s
Availability | SPARQL endpoint availability check for European Election Results took 0.9242079257965088s
Availability | VoID file availability check for European Election Results took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for European Election Results took 0.2741398811340332s
Reputation | Calculation of the PageRank for European Election Results took 0.020879507064819336s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.457069396972656e-05s
Believability | Calculation of trust value for European Election Results took 8.344650268554688e-06s
INFO | --- Analysis for european-election-results took 9.554949522018433s
Availability | SPARQL endpoint availability check for EPO patents took 0.3327200412750244s
Availability | VoID file availability check for EPO patents took 0.0005462169647216797s
Extra | Recovery of all triples for EPO patents took 28.351582527160645s
Performance | Total latancy measurement for EPO patents took 1.0373055934906006s
Amount of data | Number of triples check for EPO patents took 90.21207928657532s
Versatility | Languages check for EPO patents took 100.45723366737366s
Interpretability | Number of blank nodes check for EPO patents took 90.25227975845337s
Interpretability | RDF structures check for EPO patents took 0.3209226131439209s
Versatility | Serialization formats check for EPO patents took 0.1966569423675537s
Availability | RDF dump link check for EPO patents took 0.18311095237731934s
License | MR license check for EPO patents took 0.19783878326416016s
License | HR license check for EPO patents took 90.20548486709595s
Amount of data | Number of property check for EPO patents took 0.2853398323059082s
Understandability | Number of label check for EPO patents took 90.18849730491638s
Understandability | URI regex check for EPO patents took 0.4907386302947998s
Understandability | Vocabs check for EPO patents took 0.2640397548675537s
Verifiability | Authors check for EPO patents took 0.22082114219665527s
Verifiability | Publishers check for EPO patents took 0.2816133499145508s
Performance | Throughput check for EPO patents took 11.285654783248901s
Amount of data | Check the number of entities for EPO patents took 8.0108642578125e-05s
Verifiability | Contribs. check for EPO patents took 0.15504670143127441s
Interlinking | sameAs chians check for EPO patents took 0.15003395080566406s
Interlinking | skos check for EPO patents took 0.1807703971862793s
Interlinking | skos check for EPO patents took 0.34959864616394043s
Timeliness | dataset update frequency check for EPO patents took 0.16405367851257324s
Currency | Creation date check for EPO patents took 0.3376142978668213s
Currency | Modification date check for EPO patents took 0.3456737995147705s
Rep.Conc. | URIs length for EPO patents took 133.07064843177795s
Interoperability | New vocabularies check for EPO patents took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.18857240676879883s
Accuracy | Check Empty annotation labels for EPO patents took 21.692723035812378s
Accuracy | Check White space in annotation for EPO patents took 2.9587137699127197s
Accuracy | Check Datatype consistency for EPO patents took 4.916228532791138s
Consistency | Disjoint class check for EPO patents took 0.21058034896850586s
Consistency | Check Misplaced properties for EPO patents took 100.4915931224823s
Consistency | Check Ontology hijacking for EPO patents took 25.854819774627686s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.4532828330993652s
Consistency | Check Invalid usage of undefined properties for EPO patents took 101.49277138710022s
Conciseness | Check Extensional conciseness for EPO patents took 2.7772250175476074s
Conciseness | Check Intensional conciseness for EPO patents took 0.3922600746154785s
Security | Sign check for EPO patents took 0.18738865852355957s
Availability | Check URIs Dereferenciability for EPO patents took 1.8832781314849854s
Completeness | Calculation of interlinking completeness for EPO patents took 0.42108154296875s
Reputation | Calculation of the PageRank for EPO patents took 0.021989822387695312s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0006780624389648438s
Interlinking | Calculation of Clustering coefficient for EPO patents took 4.839897155761719e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 2.1457672119140625e-06s
Believability | Calculation of trust value for EPO patents took 1.239776611328125e-05s
INFO | --- Analysis for European_Patent_Information took 1200.0950367450714s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 8.940696716308594e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.3119652271270752s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.021088361740112305s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0006833076477050781s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.226799011230469e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 1.1920928955078125e-05s
INFO | --- Analysis for europeana-lod-v1 took 6.9559221267700195s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.3486449718475342s
Availability | VoID file availability check for Europeana SPARQL took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.26482176780700684s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020508766174316406s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.76837158203125e-05s
Believability | Calculation of trust value for Europeana SPARQL took 1.1444091796875e-05s
INFO | --- Analysis for europeana-sparql took 6.068406581878662s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.08354973793029785s
Availability | VoID file availability check for EuroSentiment took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.30779194831848145s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02115654945373535s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.790855407714844e-05s
Believability | Calculation of trust value for EuroSentiment took 1.2874603271484375e-05s
INFO | --- Analysis for eurosentiment took 3.160388231277466s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 8.678436279296875e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.2636237144470215s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.022293806076049805s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.843971252441406e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 8.344650268554688e-06s
INFO | --- Analysis for eurostat-rdf took 10.238738536834717s
Availability | SPARQL endpoint availability check for EuroVoc took 0.16595077514648438s
Availability | VoID file availability check for EuroVoc took 0.0005269050598144531s
Extra | Recovery of all triples for EuroVoc took 191.9461646080017s
Performance | Total latancy measurement for EuroVoc took 0.5661005973815918s
Amount of data | Number of triples check for EuroVoc took 82.87822914123535s
Interoperability | New terms check for EuroVoc took 62.15258502960205s
Versatility | Languages check for EuroVoc took 300.0469512939453s
Interpretability | Number of blank nodes check for EuroVoc took 20.02909779548645s
Security | Check HTTPS for EuroVoc took 0.3135826587677002s
Interpretability | RDF structures check for EuroVoc took 0.4534926414489746s
Versatility | Serialization formats check for EuroVoc took 3.249772071838379s
Availability | RDF dump link check for EuroVoc took 0.30980634689331055s
License | MR license check for EuroVoc took 0.36934375762939453s
License | HR license check for EuroVoc took 300.0667812824249s
Amount of data | Number of property check for EuroVoc took 0.1465444564819336s
Understandability | Number of label check for EuroVoc took 2.7835333347320557s
Understandability | URI regex check for EuroVoc took 0.4030120372772217s
Understandability | Vocabs check for EuroVoc took 0.10495543479919434s
Verifiability | Authors check for EuroVoc took 0.23995327949523926s
Verifiability | Publishers check for EuroVoc took 0.1651630401611328s
Performance | Throughput check for EuroVoc took 10.746537685394287s
Amount of data | Check the number of entities for EuroVoc took 8.0108642578125e-05s
Verifiability | Contribs. check for EuroVoc took 0.18485736846923828s
Interlinking | sameAs chians check for EuroVoc took 8.639264583587646s
Interlinking | skos check for EuroVoc took 0.3417990207672119s
Interlinking | skos check for EuroVoc took 0.14840388298034668s
Timeliness | dataset update frequency check for EuroVoc took 0.2094109058380127s
Currency | Creation date check for EuroVoc took 0.48114514350891113s
Currency | Modification date check for EuroVoc took 0.2619340419769287s
Rep.Conc. | URIs length for EuroVoc took 440.31271409988403s
Interoperability | New vocabularies check for EuroVoc took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.15294790267944336s
Accuracy | Check Functional Property for EuroVoc took 0.17286133766174316s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.1552257537841797s
Accuracy | Check Empty annotation labels for EuroVoc took 39.73057675361633s
Accuracy | Check White space in annotation for EuroVoc took 3.058074474334717s
Accuracy | Check Datatype consistency for EuroVoc took 2.597705841064453s
Consistency | Disjoint class check for EuroVoc took 0.14919114112854004s
Consistency | Check Misplaced properties for EuroVoc took 300.3491451740265s
Consistency | Misplaced classes for EuroVoc took 8.154160499572754s
Consistency | Check Ontology hijacking for EuroVoc took 40.52819609642029s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.3476805686950684s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.39653635025024s
Conciseness | Check Extensional conciseness for EuroVoc took 2.9520955085754395s
Conciseness | Check Intensional conciseness for EuroVoc took 0.3497941493988037s
Security | Sign check for EuroVoc took 0.11855554580688477s
Availability | Check URIs Dereferenciability for EuroVoc took 10.999147891998291s
Completeness | Calculation of interlinking completeness for EuroVoc took 0.9167253971099854s
Reputation | Calculation of the PageRank for EuroVoc took 0.02198934555053711s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 8.273124694824219e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 2.384185791015625e-06s
Believability | Calculation of trust value for EuroVoc took 1.1920928955078125e-05s
INFO | --- Analysis for eurovoc took 14164.983841657639s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 8.535385131835938e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.2728097438812256s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.02085566520690918s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.887580871582031e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 7.867813110351562e-06s
INFO | --- Analysis for euskadi-farmacias took 4.9619855880737305s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.951918363571167s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.26992058753967285s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.02093052864074707s
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.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.075599670410156e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 1.1205673217773438e-05s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.963531255722046s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.23997712135314941s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0007510185241699219s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.2670590877532959s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.343292236328125e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 1.5020370483398438e-05s
INFO | --- Analysis for eutc-productions took 6.100700855255127s
Availability | SPARQL endpoint availability check for EventMedia took 0.3317270278930664s
Availability | VoID file availability check for EventMedia took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for EventMedia took 0.26907825469970703s
Reputation | Calculation of the PageRank for EventMedia took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00011277198791503906s
Believability | Calculation of trust value for EventMedia took 1.4543533325195312e-05s
INFO | --- Analysis for event-media took 18.310288190841675s
Availability | SPARQL endpoint availability check for EventKG took 8.678436279296875e-05s
Availability | VoID file availability check for EventKG took 0.0007126331329345703s
Completeness | Calculation of interlinking completeness for EventKG took 0.2665283679962158s
Reputation | Calculation of the PageRank for EventKG took 0.021187305450439453s
Interlinking | Calculation of Degree of Connection for EventKG took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.320808410644531e-05s
Believability | Calculation of trust value for EventKG took 1.239776611328125e-05s
INFO | --- Analysis for eventkg took 4.58298397064209s
Availability | SPARQL endpoint availability check for Eventseer took 7.772070646286011s
Availability | VoID file availability check for Eventseer took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Eventseer took 0.3759288787841797s
Reputation | Calculation of the PageRank for Eventseer took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Eventseer took 5.340576171875e-05s
Believability | Calculation of trust value for Eventseer took 1.2159347534179688e-05s
INFO | --- Analysis for eventseer took 10.359570980072021s
Availability | SPARQL endpoint availability check for Face Link took 4.363059997558594e-05s
Availability | VoID file availability check for Face Link took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Face Link took 0.26625514030456543s
Reputation | Calculation of the PageRank for Face Link took 0.02058887481689453s
Interlinking | Calculation of Degree of Connection for Face Link took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.2901763916015625e-05s
Believability | Calculation of trust value for Face Link took 1.1682510375976562e-05s
INFO | --- Analysis for Face_Link took 2.391148090362549s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.46240854263305664s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0002732276916503906s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 110.9505877494812s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.8709533214569092s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.634032011032104s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 14.106985807418823s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.1607406139374s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.1921937465667725s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.26889705657958984s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.742695331573486s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.25380802154541016s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5022821426391602s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.1402893066406s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.17433428764343262s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.54896879196167s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.6325180530548096s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2424759864807129s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18448400497436523s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21966767311096191s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.598793506622314s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.817413330078125e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.17999672889709473s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.17797398567199707s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.43915486335754395s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.46555161476135254s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.601757764816284s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.42527222633361816s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.22491192817687988s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 146.4167993068695s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.17953729629516602s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3361701965332031s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.34786462783813477s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 34.51450562477112s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6345198154449463s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6103808879852295s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.17672348022460938s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 86.89831447601318s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.220775842666626s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 30.96142554283142s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.2571513652801514s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 87.39383745193481s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.698180913925171s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5477480888366699s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.7556343078613281s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.73136591911316s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4534919261932373s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.021816730499267578s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 6.008148193359375e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.363059997558594e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0728836059570312e-05s
INFO | --- Analysis for FADN_(2019) took 2214.4955434799194s
Availability | SPARQL endpoint availability check for FAMEData took 8.845329284667969e-05s
Availability | VoID file availability check for FAMEData took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for FAMEData took 0.26692843437194824s
Reputation | Calculation of the PageRank for FAMEData took 0.021500349044799805s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.266334533691406e-05s
Believability | Calculation of trust value for FAMEData took 1.239776611328125e-05s
INFO | --- Analysis for famedata took 5.808239459991455s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 8.893013000488281e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.26326751708984375s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.02126789093017578s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.608268737792969e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 8.821487426757812e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 9.684837102890015s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.08973312377929688s
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 0.2641110420227051s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.021704435348510742s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0001010894775390625s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for fao-linked-data took 2.5452253818511963s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 8.7738037109375e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.26894044876098633s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.0207672119140625s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.0994415283203125e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.0967254638671875e-05s
INFO | --- Analysis for FAO_species took 2.447715997695923s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.54212760925293s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.2674534320831299s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.020905494689941406s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.839897155761719e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.2159347534179688e-05s
INFO | --- Analysis for farmbio-chembl took 67.30970191955566s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.506111145019531e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.267596960067749s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.020906448364257812s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.314018249511719e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.2159347534179688e-05s
INFO | --- Analysis for fatimazahra took 2.4140031337738037s
Availability | SPARQL endpoint availability check for FHIR STU3 took 8.368492126464844e-05s
Availability | VoID file availability check for FHIR STU3 took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.26415061950683594s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.023291826248168945s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 3.075599670410156e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.049041748046875e-05s
INFO | --- Analysis for FHIR_STU3 took 2.765291452407837s
Availability | SPARQL endpoint availability check for FiESTA took 4.291534423828125e-05s
Availability | VoID file availability check for FiESTA took 0.0008516311645507812s
Completeness | Calculation of interlinking completeness for FiESTA took 0.2784264087677002s
Reputation | Calculation of the PageRank for FiESTA took 0.021956682205200195s
Interlinking | Calculation of Degree of Connection for FiESTA took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0010023117065429688s
Interlinking | Calculation of Clustering coefficient for FiESTA took 5.841255187988281e-05s
Believability | Calculation of trust value for FiESTA took 1.8358230590820312e-05s
INFO | --- Analysis for fiesta took 12.636292695999146s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.363059997558594e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.26606059074401855s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02263641357421875s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.123283386230469e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0728836059570312e-05s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.396153688430786s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 4.100799560546875e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.28914713859558105s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.02287578582763672s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 6.794929504394531e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 8.58306884765625e-06s
INFO | --- Analysis for finnish-municipalities took 3.511580467224121s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.17981266975402832s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0005676746368408203s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 114.28715562820435s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 0.861365556716919s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 9.166687965393066s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 13.979540824890137s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.1893630027771s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 1.9413282871246338s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.25450587272644043s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 8.424245834350586s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.2634162902832031s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.5418696403503418s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.1462514400482s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.18265247344970703s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 2.048530101776123s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 0.718757152557373s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.25594496726989746s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.18028044700622559s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.22701668739318848s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 10.68528938293457s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 7.343292236328125e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.18407392501831055s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.17868661880493164s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4265444278717041s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.3972134590148926s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 5.859401226043701s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.42101073265075684s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.22710967063903809s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 155.79936623573303s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.17483735084533691s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.3589365482330322s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.3166072368621826s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 38.149659395217896s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.6162941455841064s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.6247239112854004s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.1747448444366455s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 87.42203950881958s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.085310459136963s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 29.13179636001587s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.251272201538086s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 88.982675075531s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.690725088119507s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.4771602153778076s
Security | Sign check for Norway fishery stocks dataset @PSNC took 0.7952003479003906s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 11.54727292060852s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.7618966102600098s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.0222318172454834s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 3.910064697265625e-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.4066696166992188e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 2232.998443365097s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.1961669921875e-05s
Availability | VoID file availability check for Fishes of Texas took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.2715456485748291s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.020971059799194336s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.153915405273438e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.0251998901367188e-05s
INFO | --- Analysis for fishes-of-texas took 3.1242363452911377s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.363059997558594e-05s
Availability | VoID file availability check for flickr? wrappr took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.2891240119934082s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020910024642944336s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.202957153320312e-05s
Believability | Calculation of trust value for flickr? wrappr took 1.0967254638671875e-05s
INFO | --- Analysis for flickr-wrappr took 3.2217154502868652s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.315376281738281e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.27359747886657715s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.020823240280151367s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.552436828613281e-05s
Believability | Calculation of trust value for Future land use simulation model took 9.775161743164062e-06s
INFO | --- Analysis for FLUS took 128.74202299118042s
Availability | SPARQL endpoint availability check for Flybase took 1.068845272064209s
Availability | VoID file availability check for Flybase took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Flybase took 0.2717411518096924s
Reputation | Calculation of the PageRank for Flybase took 0.021090984344482422s
Interlinking | Calculation of Degree of Connection for Flybase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Flybase took 4.673004150390625e-05s
Believability | Calculation of trust value for Flybase took 1.0728836059570312e-05s
INFO | --- Analysis for flybase took 5.0462212562561035s
Availability | SPARQL endpoint availability check for Flyted took 0.8042168617248535s
Availability | VoID file availability check for Flyted took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Flyted took 0.26388049125671387s
Reputation | Calculation of the PageRank for Flyted took 0.020787715911865234s
Interlinking | Calculation of Degree of Connection for Flyted took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Flyted took 2.86102294921875e-05s
Believability | Calculation of trust value for Flyted took 1.1444091796875e-05s
INFO | --- Analysis for flyted took 5.054590463638306s
Availability | SPARQL endpoint availability check for Foodista took 1.416398525238037s
Availability | VoID file availability check for Foodista took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for Foodista took 0.2640213966369629s
Reputation | Calculation of the PageRank for Foodista took 0.023632049560546875s
Interlinking | Calculation of Degree of Connection for Foodista took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.075599670410156e-05s
Believability | Calculation of trust value for Foodista took 1.049041748046875e-05s
INFO | --- Analysis for foodista took 8.879274129867554s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.16715359687805176s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2691628932952881s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.022716760635375977s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.43865966796875e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.0967254638671875e-05s
INFO | --- Analysis for foodpedia took 2.5952398777008057s
Availability | SPARQL endpoint availability check for FrameBase schema took 8.463859558105469e-05s
Availability | VoID file availability check for FrameBase schema took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.2664453983306885s
Reputation | Calculation of the PageRank for FrameBase schema took 0.02148747444152832s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.220008850097656e-05s
Believability | Calculation of trust value for FrameBase schema took 9.5367431640625e-06s
INFO | --- Analysis for framebase-schema took 2.964771270751953s
Availability | SPARQL endpoint availability check for Framester took 8.344650268554688e-05s
Availability | VoID file availability check for Framester took 0.0008337497711181641s
Completeness | Calculation of interlinking completeness for Framester took 0.26175642013549805s
Reputation | Calculation of the PageRank for Framester took 0.02170252799987793s
Interlinking | Calculation of Degree of Connection for Framester took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Framester took 7.367134094238281e-05s
Believability | Calculation of trust value for Framester took 1.0728836059570312e-05s
INFO | --- Analysis for framester took 3.6024394035339355s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.0472104549407959s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2644650936126709s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.020844221115112305s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.463859558105469e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for frb-linked-data took 2.4898014068603516s
Availability | SPARQL endpoint availability check for 1989shack Inc. E-Commerce  took 4.291534423828125e-05s
Availability | VoID file availability check for 1989shack Inc. E-Commerce  took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for 1989shack Inc. E-Commerce  took 0.26587748527526855s
Reputation | Calculation of the PageRank for 1989shack Inc. E-Commerce  took 0.02071523666381836s
Interlinking | Calculation of Degree of Connection for 1989shack Inc. E-Commerce  took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 1989shack Inc. E-Commerce  took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for 1989shack Inc. E-Commerce  took 0.0002655982971191406s
Believability | Calculation of trust value for 1989shack Inc. E-Commerce  took 1.0251998901367188e-05s
INFO | --- Analysis for freebase took 3.663503646850586s
Availability | SPARQL endpoint availability check for Freeyork took 0.00011539459228515625s
Availability | VoID file availability check for Freeyork took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Freeyork took 0.2717146873474121s
Reputation | Calculation of the PageRank for Freeyork took 0.020661354064941406s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010418891906738281s
Believability | Calculation of trust value for Freeyork took 9.5367431640625e-06s
INFO | --- Analysis for freeyork-org took 2.961453437805176s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.626173734664917s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.26959800720214844s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.020649194717407227s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.224082946777344e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 8.106231689453125e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.389252662658691s
Availability | SPARQL endpoint availability check for DailyMed took 0.6105334758758545s
Availability | VoID file availability check for DailyMed took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for DailyMed took 0.2779674530029297s
Reputation | Calculation of the PageRank for DailyMed took 0.02249312400817871s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.202957153320312e-05s
Believability | Calculation of trust value for DailyMed took 1.1682510375976562e-05s
INFO | --- Analysis for fu-berlin-dailymed took 5.150727272033691s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.620694637298584s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.2639181613922119s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.021181344985961914s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.344650268554688e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.0967254638671875e-05s
INFO | --- Analysis for fu-berlin-dblp took 4.1409924030303955s
Availability | SPARQL endpoint availability check for Diseasome took 0.6195857524871826s
Availability | VoID file availability check for Diseasome took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for Diseasome took 0.26689982414245605s
Reputation | Calculation of the PageRank for Diseasome took 0.02030491828918457s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00010895729064941406s
Believability | Calculation of trust value for Diseasome took 1.2159347534179688e-05s
INFO | --- Analysis for fu-berlin-diseasome took 5.16904616355896s
Availability | SPARQL endpoint availability check for DrugBank took 0.6154553890228271s
Availability | VoID file availability check for DrugBank took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2654595375061035s
Reputation | Calculation of the PageRank for DrugBank took 0.020722150802612305s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00010943412780761719s
Believability | Calculation of trust value for DrugBank took 1.0728836059570312e-05s
INFO | --- Analysis for fu-berlin-drugbank took 5.153223991394043s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.617185115814209s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.2726268768310547s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.021791696548461914s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 2.956390380859375e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 4.1310319900512695s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.6010797023773193s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.2691304683685303s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.023468494415283203s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 8.153915405273438e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 8.344650268554688e-06s
INFO | --- Analysis for fu-berlin-euraxess took 5.462111711502075s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.6038212776184082s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.27090001106262207s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.022335290908813477s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.677078247070312e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 8.821487426757812e-06s
INFO | --- Analysis for fu-berlin-eures took 4.123894691467285s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.5974586009979248s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.27095818519592285s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.751319885253906e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 9.059906005859375e-06s
INFO | --- Analysis for fu-berlin-eurostat took 4.632419586181641s
Availability | SPARQL endpoint availability check for MediCare took 0.6102449893951416s
Availability | VoID file availability check for MediCare took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for MediCare took 0.26842331886291504s
Reputation | Calculation of the PageRank for MediCare took 0.02115321159362793s
Interlinking | Calculation of Degree of Connection for MediCare took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.100799560546875e-05s
Believability | Calculation of trust value for MediCare took 1.0251998901367188e-05s
INFO | --- Analysis for fu-berlin-medicare took 4.640758514404297s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.6113903522491455s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.2707340717315674s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020789623260498047s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.224082946777344e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 8.821487426757812e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.091027021408081s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.6028187274932861s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.2702445983886719s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.021030426025390625s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.250640869140625e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.0728836059570312e-05s
INFO | --- Analysis for fu-berlin-sider took 4.628480672836304s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.6165461540222168s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.28687381744384766s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.021295785903930664s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.605552673339844e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.1205673217773438e-05s
INFO | --- Analysis for fu-berlin-stitch took 4.167252063751221s
Availability | SPARQL endpoint availability check for fvdb took 8.678436279296875e-05s
Availability | VoID file availability check for fvdb took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for fvdb took 0.26770544052124023s
Reputation | Calculation of the PageRank for fvdb took 0.021430492401123047s
Interlinking | Calculation of Degree of Connection for fvdb took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for fvdb took 2.8848648071289062e-05s
Believability | Calculation of trust value for fvdb took 1.1444091796875e-05s
INFO | --- Analysis for fv took 12.423082828521729s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 8.58306884765625e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.2733900547027588s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.021089553833007812s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.170967102050781e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 1.049041748046875e-05s
INFO | --- Analysis for GACS took 3.056529998779297s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.00010418891906738281s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007627010345458984s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.26356983184814453s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.02091360092163086s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.00543212890625e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 4.798227787017822s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 9.560585021972656e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.27268123626708984s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.02164006233215332s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00010418891906738281s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.0728836059570312e-05s
INFO | --- Analysis for garnicaplywood took 5.670661449432373s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.982948303222656e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.26644134521484375s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.020673036575317383s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 8.893013000488281e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.239776611328125e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.9794065952301025s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.27783203125s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.2637290954589844s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.021343231201171875s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 8.96453857421875e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.1205673217773438e-05s
INFO | --- Analysis for gemet took 4.67498254776001s
Availability | SPARQL endpoint availability check for gemet-annotated took 8.368492126464844e-05s
Availability | VoID file availability check for gemet-annotated took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.26093387603759766s
Reputation | Calculation of the PageRank for gemet-annotated took 0.021260976791381836s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.552436828613281e-05s
Believability | Calculation of trust value for gemet-annotated took 1.1682510375976562e-05s
INFO | --- Analysis for gemet-annotated took 2.9216864109039307s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.6723752021789551s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.00041484832763671875s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.2730846405029297s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.021665334701538086s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.910064697265625e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.1444091796875e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.008430480957031s
Availability | SPARQL endpoint availability check for Super Ontology took 1.6147046089172363s
Availability | VoID file availability check for Super Ontology took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.27117156982421875s
Reputation | Calculation of the PageRank for Super Ontology took 0.02119755744934082s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for Super Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 5.6780617237091064s
Availability | SPARQL endpoint availability check for Geographic detector model took 8.463859558105469e-05s
Availability | VoID file availability check for Geographic detector model took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.32161831855773926s
Reputation | Calculation of the PageRank for Geographic detector model took 0.02087688446044922s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.170967102050781e-05s
Believability | Calculation of trust value for Geographic detector model took 1.0728836059570312e-05s
INFO | --- Analysis for GeoDetector took 23.803943157196045s
Availability | SPARQL endpoint availability check for geodomainwn took 5.0067901611328125e-05s
Availability | VoID file availability check for geodomainwn took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.27294921875s
Reputation | Calculation of the PageRank for geodomainwn took 0.021143674850463867s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.458427429199219e-05s
Believability | Calculation of trust value for geodomainwn took 1.1205673217773438e-05s
INFO | --- Analysis for geodomainwn took 6.696027755737305s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.172325134277344e-05s
Availability | VoID file availability check for GeoEcuador took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.26131629943847656s
Reputation | Calculation of the PageRank for GeoEcuador took 0.0216982364654541s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.461143493652344e-05s
Believability | Calculation of trust value for GeoEcuador took 1.2636184692382812e-05s
INFO | --- Analysis for geoecuador took 12.5245361328125s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.0724103450775146s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.2693030834197998s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.02075481414794922s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.341934204101562e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.2159347534179688e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 48.47119379043579s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.4192206859588623s
Availability | VoID file availability check for GeoLinkedData took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.2644193172454834s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.225440979003906e-05s
Believability | Calculation of trust value for GeoLinkedData took 1.0013580322265625e-05s
INFO | --- Analysis for geolinkeddata took 4.576812028884888s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.1759777069091797s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0006539821624755859s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 8.821022510528564s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.33513522148132324s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.1281442642211914s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.3246285915374756s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.18287444114685059s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.14826631546020508s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.1820068359375s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.08826041221618652s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.08562350273132324s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.06038022041320801s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.08477258682250977s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.8726651668548584s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.08858442306518555s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.0920252799987793s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.11962103843688965s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.08492541313171387s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.061463356018066406s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.08393979072570801s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.313884735107422s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 6.890296936035156e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.06083989143371582s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.06087493896484375s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.08526253700256348s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.06156182289123535s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.06144070625305176s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1469593048095703s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.14914584159851074s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.221597671508789s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 0.7624273300170898s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.08415699005126953s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06050539016723633s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06006741523742676s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.2815389633178711s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007145881652832031s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.22670483589172363s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.061043739318847656s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.19719243049621582s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5074751377105713s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.085118293762207s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.3929762840270996s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.5589525699615479s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.17779278755187988s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.06094670295715332s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 0.9762728214263916s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.2649698257446289s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020817279815673828s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 7.987022399902344e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 2.302098035812378s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 1.1682510375976562e-05s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 52.62347483634949s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 9.012222290039062e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.2747383117675781s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004949569702148438s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.0728836059570312e-05s
INFO | --- Analysis for geonames-semantic-web took 3.2046618461608887s
Availability | SPARQL endpoint availability check for Geospatial World  took 8.392333984375e-05s
Availability | VoID file availability check for Geospatial World  took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.26737022399902344s
Reputation | Calculation of the PageRank for Geospatial World  took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.000102996826171875s
Believability | Calculation of trust value for Geospatial World  took 1.0728836059570312e-05s
INFO | --- Analysis for geospatialworld-net took 2.9251341819763184s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5287714004516602s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0010981559753417969s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.27778053283691406s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.02104949951171875s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00013494491577148438s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 5.9604644775390625e-06s
INFO | --- Analysis for geospecies took 5.7241129875183105s
Availability | SPARQL endpoint availability check for GeoWordNet took 8.869171142578125e-05s
Availability | VoID file availability check for GeoWordNet took 0.0006730556488037109s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.2632331848144531s
Reputation | Calculation of the PageRank for GeoWordNet took 0.020799875259399414s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.078315734863281e-05s
Believability | Calculation of trust value for GeoWordNet took 1.049041748046875e-05s
INFO | --- Analysis for geowordnet took 9.681116104125977s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.05745387077331543s
Availability | VoID file availability check for German labor law thesaurus took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.2705237865447998s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.020848512649536133s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 7.700920104980469e-05s
Believability | Calculation of trust value for German labor law thesaurus took 1.0728836059570312e-05s
INFO | --- Analysis for german-labor-law-thesaurus took 2.4970860481262207s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.172325134277344e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.26247739791870117s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.022406578063964844s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.00543212890625e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.1205673217773438e-05s
INFO | --- Analysis for germlex took 2.76720929145813s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 2.5057168006896973s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2136983871459961s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.27086901664733887s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.021556854248046875s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.940696716308594e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.2874603271484375e-05s
INFO | --- Analysis for gesis-thesoz took 7.987941265106201s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.7016031742095947s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.26263928413391113s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.02089667320251465s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.557868957519531e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 1.1205673217773438e-05s
INFO | --- Analysis for getty-aat took 19.569053649902344s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.3130676746368408s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.27222323417663574s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.078315734863281e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.0967254638671875e-05s
INFO | --- Analysis for getty-tgn took 17.518841981887817s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 7.14311671257019s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.26825737953186035s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.02186298370361328s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0008466243743896484s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.314018249511719e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 5.4836273193359375e-06s
INFO | --- Analysis for gipuzkoademografia took 30.469018697738647s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 8.893013000488281e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.26873779296875s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.020437002182006836s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 2.8133392333984375e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 1.0967254638671875e-05s
INFO | --- Analysis for glastonbury-2011 took 5.238929510116577s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 8.845329284667969e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.2628026008605957s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.022331953048706055s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.6253204345703125e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 1.1444091796875e-05s
INFO | --- Analysis for global-hunger-index-2011 took 3.374830961227417s
Availability | SPARQL endpoint availability check for Glottolog took 9.274482727050781e-05s
Availability | VoID file availability check for Glottolog took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2740743160247803s
Reputation | Calculation of the PageRank for Glottolog took 0.023287057876586914s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.793571472167969e-05s
Believability | Calculation of trust value for Glottolog took 1.1920928955078125e-05s
INFO | --- Analysis for glottolog took 6.0030670166015625s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 9.083747863769531e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.287273645401001s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.022431373596191406s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010538101196289062s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.1920928955078125e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 10.683018684387207s
Availability | SPARQL endpoint availability check for 1121 took 8.678436279296875e-05s
Availability | VoID file availability check for 1121 took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for 1121 took 0.26862359046936035s
Reputation | Calculation of the PageRank for 1121 took 0.02086496353149414s
Interlinking | Calculation of Degree of Connection for 1121 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.0994415283203125e-05s
Believability | Calculation of trust value for 1121 took 1.3113021850585938e-05s
INFO | --- Analysis for God_ took 3.041123628616333s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 8.702278137207031e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.260242223739624s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.02240443229675293s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.125999450683594e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.1682510375976562e-05s
INFO | --- Analysis for gold took 3.7803001403808594s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.172325134277344e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0011034011840820312s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.2798123359680176s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.02096390724182129s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 7.200241088867188e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 1.1682510375976562e-05s
INFO | --- Analysis for googleart-wrapper took 2.808293342590332s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.07619476318359375s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0008363723754882812s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.27784013748168945s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020743846893310547s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.361701965332031e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.1682510375976562e-05s
INFO | --- Analysis for govagribus-denmark took 34.637953758239746s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.3946924209594727s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.2640345096588135s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020776748657226562s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.177757263183594e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 23.975290536880493s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.7185192108154297s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0007283687591552734s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.26714539527893066s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.021168231964111328s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.630752563476562e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 8.821487426757812e-06s
INFO | --- Analysis for govtrack took 10.872831106185913s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 9.036064147949219e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.3485987186431885s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.02268075942993164s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 0.00011563301086425781s
Believability | Calculation of trust value for greek-administrative-geography took 1.1920928955078125e-05s
INFO | --- Analysis for greek-administrative-geography took 2.550926923751831s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.1669178009033203s
Availability | VoID file availability check for Greek Wordnet took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.2704761028289795s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.021484375s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.124641418457031e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.2874603271484375e-05s
INFO | --- Analysis for greek-wordnet took 2.6115832328796387s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.30056071281433105s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0006120204925537109s
Extra | Recovery of all triples for Greek prisons releases Jan 2018 - Dec 2023 took 15.220997333526611s
Performance | Total latancy measurement for Greek prisons releases Jan 2018 - Dec 2023 took 0.5753688812255859s
Amount of data | Number of triples check for Greek prisons releases Jan 2018 - Dec 2023 took 0.702103853225708s
Interoperability | New terms check for Greek prisons releases Jan 2018 - Dec 2023 took 1.976365327835083s
Versatility | Languages check for Greek prisons releases Jan 2018 - Dec 2023 took 1.8968875408172607s
Interpretability | Number of blank nodes check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5064971446990967s
Interpretability | RDF structures check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1260700225830078s
Versatility | Serialization formats check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12040305137634277s
Availability | RDF dump link check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11408615112304688s
License | MR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11801886558532715s
License | HR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5339267253875732s
Amount of data | Number of property check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11945867538452148s
Understandability | Number of label check for Greek prisons releases Jan 2018 - Dec 2023 took 0.17615175247192383s
Understandability | URI regex check for Greek prisons releases Jan 2018 - Dec 2023 took 0.22944188117980957s
Understandability | Vocabs check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11517786979675293s
Verifiability | Authors check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11540961265563965s
Verifiability | Publishers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1153421401977539s
Performance | Throughput check for Greek prisons releases Jan 2018 - Dec 2023 took 10.324284315109253s
Amount of data | Check the number of entities for Greek prisons releases Jan 2018 - Dec 2023 took 0.00011110305786132812s
Verifiability | Contribs. check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11448931694030762s
Interlinking | sameAs chians check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11492753028869629s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11582422256469727s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11676216125488281s
Timeliness | dataset update frequency check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11501145362854004s
Currency | Creation date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.23353981971740723s
Currency | Modification date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.23531651496887207s
Rep.Conc. | URIs length for Greek prisons releases Jan 2018 - Dec 2023 took 8.083868980407715s
Interoperability | New vocabularies check for Greek prisons releases Jan 2018 - Dec 2023 took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11568450927734375s
Accuracy | Check Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.11290168762207031s
Accuracy | Check Inverse Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.11223554611206055s
Accuracy | Check Empty annotation labels for Greek prisons releases Jan 2018 - Dec 2023 took 2.0860495567321777s
Accuracy | Check White space in annotation for Greek prisons releases Jan 2018 - Dec 2023 took 0.28590965270996094s
Accuracy | Check Datatype consistency for Greek prisons releases Jan 2018 - Dec 2023 took 4.706545829772949s
Consistency | Disjoint class check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11888837814331055s
Consistency | Check Misplaced properties for Greek prisons releases Jan 2018 - Dec 2023 took 1.1345090866088867s
Consistency | Check Ontology hijacking for Greek prisons releases Jan 2018 - Dec 2023 took 2.8856329917907715s
Consistency | Check Invalid usage of undefined classes for Greek prisons releases Jan 2018 - Dec 2023 took 1.295884370803833s
Consistency | Check Invalid usage of undefined properties for Greek prisons releases Jan 2018 - Dec 2023 took 2.45954966545105s
Conciseness | Check Extensional conciseness for Greek prisons releases Jan 2018 - Dec 2023 took 2.8062665462493896s
Security | Sign check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11375236511230469s
Availability | Check URIs Dereferenciability for Greek prisons releases Jan 2018 - Dec 2023 took 9.270877838134766s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.26696252822875977s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.02119731903076172s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.3828277587890625e-05s
Interoperability | Check the re-using of existing vocabs for Greek prisons releases Jan 2018 - Dec 2023 took 1.9073486328125e-06s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 1.1444091796875e-05s
INFO | --- Analysis for greek_prisons_releases took 89.21483302116394s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.6894431114196777s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2614264488220215s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.021043777465820312s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.748603820800781e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.1920928955078125e-05s
INFO | --- Analysis for greekchildrensartmuseum took 4.261447906494141s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 0.0001552104949951172s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.2708570957183838s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.021043777465820312s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00011539459228515625s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.0967254638671875e-05s
INFO | --- Analysis for green-competitiveness-gnoss took 7.773959636688232s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.3587031364440918s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.26175642013549805s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.021109819412231445s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 5.269050598144531e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 1.1682510375976562e-05s
INFO | --- Analysis for grrp took 2.825479745864868s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.2077503204345703s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.2666356563568115s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020766735076904297s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.771087646484375e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 4.5299530029296875e-06s
INFO | --- Analysis for grrt took 2.6532046794891357s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.1606051921844482s
Availability | VoID file availability check for Geological Timescale took 0.0006344318389892578s
Extra | Recovery of all triples for Geological Timescale took 4.171252012252808s
Performance | Total latancy measurement for Geological Timescale took 3.8138644695281982s
Amount of data | Number of triples check for Geological Timescale took 1.1250927448272705s
Interoperability | New terms check for Geological Timescale took 1.534078598022461s
Versatility | Languages check for Geological Timescale took 1.8394627571105957s
Interpretability | Number of blank nodes check for Geological Timescale took 0.9870975017547607s
Security | Check HTTPS for Geological Timescale took 0.33923888206481934s
Interpretability | RDF structures check for Geological Timescale took 0.3929409980773926s
Versatility | Serialization formats check for Geological Timescale took 0.41835951805114746s
Availability | RDF dump link check for Geological Timescale took 1.0176904201507568s
License | MR license check for Geological Timescale took 0.9494633674621582s
License | HR license check for Geological Timescale took 2.924233913421631s
Amount of data | Number of property check for Geological Timescale took 0.7499167919158936s
Understandability | Number of label check for Geological Timescale took 0.9670050144195557s
Understandability | URI regex check for Geological Timescale took 0.7866666316986084s
Understandability | Vocabs check for Geological Timescale took 0.394763708114624s
Verifiability | Authors check for Geological Timescale took 1.3332421779632568s
Verifiability | Publishers check for Geological Timescale took 0.9304735660552979s
Performance | Throughput check for Geological Timescale took 16.934394359588623s
Amount of data | Check the number of entities for Geological Timescale took 0.01944565773010254s
Verifiability | Contribs. check for Geological Timescale took 0.9489648342132568s
Interlinking | sameAs chians check for Geological Timescale took 2.845568895339966s
Interlinking | skos check for Geological Timescale took 0.9683020114898682s
Interlinking | skos check for Geological Timescale took 0.37838292121887207s
Timeliness | dataset update frequency check for Geological Timescale took 0.9513723850250244s
Currency | Creation date check for Geological Timescale took 1.7316389083862305s
Currency | Modification date check for Geological Timescale took 0.4069788455963135s
Rep.Conc. | URIs length for Geological Timescale took 2.0640387535095215s
Interoperability | New vocabularies check for Geological Timescale took 5.049669027328491s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 3.9727327823638916s
Accuracy | Check Functional Property for Geological Timescale took 0.40314388275146484s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.9681470394134521s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.3060896396636963s
Accuracy | Check White space in annotation for Geological Timescale took 0.016452789306640625s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07335877418518066s
Consistency | Disjoint class check for Geological Timescale took 0.3861691951751709s
Consistency | Check Misplaced properties for Geological Timescale took 0.8241958618164062s
Consistency | Misplaced classes for Geological Timescale took 0.4964780807495117s
Consistency | Check Ontology hijacking for Geological Timescale took 2.966341733932495s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.1425371170043945s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.1391212940216064s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.050460100173950195s
Conciseness | Check Intensional conciseness for Geological Timescale took 3.0950803756713867s
Security | Sign check for Geological Timescale took 1.7722289562225342s
Availability | Check URIs Dereferenciability for Geological Timescale took 4.362123012542725s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.26433420181274414s
Reputation | Calculation of the PageRank for Geological Timescale took 0.02072739601135254s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.000820159912109375s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 7.367134094238281e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 1.516775131225586s
Believability | Calculation of trust value for Geological Timescale took 1.239776611328125e-05s
INFO | --- Analysis for GTS took 134.57396721839905s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.2616255283355713s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.02191925048828125s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 4.1484832763671875e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for GTS-ont took 2.7110304832458496s
Availability | SPARQL endpoint availability check for GUTSTOK  took 8.487701416015625e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.26634955406188965s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.020913362503051758s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.0517578125e-05s
Believability | Calculation of trust value for GUTSTOK  took 1.1682510375976562e-05s
INFO | --- Analysis for Guillaume_Forget took 2.476078748703003s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.124641418457031e-05s
Availability | VoID file availability check for Project Gutenberg took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.25841760635375977s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.021039485931396484s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.866455078125e-05s
Believability | Calculation of trust value for Project Gutenberg took 1.0967254638671875e-05s
INFO | --- Analysis for gutenberg took 9.022043228149414s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.172325134277344e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007457733154296875s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.3414266109466553s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.266334533691406e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.0251998901367188e-05s
INFO | --- Analysis for gwa-ili took 5.046716690063477s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.410743713378906e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.26952433586120605s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.0517578125e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 8.58306884765625e-06s
INFO | --- Analysis for GWR took 19.936841011047363s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.100799560546875e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.2692742347717285s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.021994590759277344s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 2.86102294921875e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 1.1444091796875e-05s
INFO | --- Analysis for HASM took 28.774701356887817s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 3.836988687515259s
Availability | VoID file availability check for HealthCare Ontology took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.263735294342041s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.020837068557739258s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.600120544433594e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for HealthCare_Ontology took 6.869105577468872s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.100799560546875e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.27440381050109863s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.022690534591674805s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.222724914550781e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 1.1682510375976562e-05s
INFO | --- Analysis for heartfailure took 2.820388078689575s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 22.08307719230652s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.26774168014526367s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.02079463005065918s
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.8358230590820312e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 4.649162292480469e-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.1682510375976562e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 118.83170628547668s
Availability | SPARQL endpoint availability check for Hedatuz took 0.22792840003967285s
Availability | VoID file availability check for Hedatuz took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.26263904571533203s
Reputation | Calculation of the PageRank for Hedatuz took 0.02069878578186035s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.790855407714844e-05s
Believability | Calculation of trust value for Hedatuz took 1.239776611328125e-05s
INFO | --- Analysis for hedatuz took 3.017740488052368s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.09660458564758301s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.00043201446533203125s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2661314010620117s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012612342834472656s
Believability | Calculation of trust value for Hellenic Fire Brigade took 9.059906005859375e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.5874204635620117s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.017037391662597656s
Availability | VoID file availability check for Hellenic Police took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.26360321044921875s
Reputation | Calculation of the PageRank for Hellenic Police took 0.021385908126831055s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00012826919555664062s
Believability | Calculation of trust value for Hellenic Police took 8.821487426757812e-06s
INFO | --- Analysis for hellenic-police took 2.4766368865966797s
Availability | SPARQL endpoint availability check for Hermos took 4.267692565917969e-05s
Availability | VoID file availability check for Hermos took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for Hermos took 0.2659726142883301s
Reputation | Calculation of the PageRank for Hermos took 0.020862102508544922s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Hermos took 3.0279159545898438e-05s
Believability | Calculation of trust value for Hermos took 1.0967254638671875e-05s
INFO | --- Analysis for Hermos took 2.9029757976531982s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.506111145019531e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.27336740493774414s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 2.8848648071289062e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 1.1205673217773438e-05s
INFO | --- Analysis for Himanshu_Mahawar took 2.3877806663513184s
Availability | SPARQL endpoint availability check for HITO took 0.37416625022888184s
Availability | VoID file availability check for HITO took 0.0005815029144287109s
Extra | Recovery of all triples for HITO took 1.695741891860962s
Performance | Total latancy measurement for HITO took 0.888606071472168s
Amount of data | Number of triples check for HITO took 0.17276358604431152s
Interoperability | New terms check for HITO took 1.3126013278961182s
Versatility | Languages check for HITO took 0.19675183296203613s
Interpretability | Number of blank nodes check for HITO took 0.16946744918823242s
Interpretability | RDF structures check for HITO took 0.18450927734375s
Versatility | Serialization formats check for HITO took 0.17622947692871094s
Availability | RDF dump link check for HITO took 0.16613245010375977s
License | MR license check for HITO took 0.1821744441986084s
License | HR license check for HITO took 0.20685982704162598s
Amount of data | Number of property check for HITO took 0.18904757499694824s
Understandability | Number of label check for HITO took 0.19698190689086914s
Understandability | URI regex check for HITO took 0.34429502487182617s
Understandability | Vocabs check for HITO took 0.1791973114013672s
Verifiability | Authors check for HITO took 0.17510128021240234s
Verifiability | Publishers check for HITO took 0.1689591407775879s
Performance | Throughput check for HITO took 10.459786415100098s
Amount of data | Check the number of entities for HITO took 7.224082946777344e-05s
Verifiability | Contribs. check for HITO took 0.17881393432617188s
Interlinking | sameAs chians check for HITO took 0.17763376235961914s
Interlinking | skos check for HITO took 0.18665814399719238s
Interlinking | skos check for HITO took 0.18476343154907227s
Timeliness | dataset update frequency check for HITO took 0.18686985969543457s
Currency | Creation date check for HITO took 0.36813926696777344s
Currency | Modification date check for HITO took 0.3486156463623047s
Rep.Conc. | URIs length for HITO took 0.9715743064880371s
Interoperability | New vocabularies check for HITO took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.16840624809265137s
Accuracy | Check Functional Property for HITO took 0.1840991973876953s
Accuracy | Check Inverse Functional Property for HITO took 0.1676344871520996s
Accuracy | Check Empty annotation labels for HITO took 0.45356082916259766s
Accuracy | Check White space in annotation for HITO took 0.013108491897583008s
Accuracy | Check Datatype consistency for HITO took 0.07244658470153809s
Consistency | Disjoint class check for HITO took 0.17708873748779297s
Consistency | Check Misplaced properties for HITO took 0.4669835567474365s
Consistency | Misplaced classes for HITO took 0.35505080223083496s
Consistency | Check Ontology hijacking for HITO took 1.5833415985107422s
Consistency | Check Invalid usage of undefined classes for HITO took 1.1434326171875s
Consistency | Check Invalid usage of undefined properties for HITO took 1.401850700378418s
Conciseness | Check Extensional conciseness for HITO took 0.05982232093811035s
Conciseness | Check Intensional conciseness for HITO took 0.1761929988861084s
Security | Sign check for HITO took 0.17916274070739746s
Availability | Check URIs Dereferenciability for HITO took 1577.860026359558s
Completeness | Calculation of interlinking completeness for HITO took 0.3561971187591553s
Reputation | Calculation of the PageRank for HITO took 0.020810842514038086s
Interlinking | Calculation of Degree of Connection for HITO took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for HITO took 9.369850158691406e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 2.1457672119140625e-06s
Believability | Calculation of trust value for HITO took 1.239776611328125e-05s
INFO | --- Analysis for hito took 1626.485421180725s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 14.661241054534912s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0003910064697265625s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.27121758460998535s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.02063155174255371s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 3.0279159545898438e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 1.1444091796875e-05s
INFO | --- Analysis for Hoa_Thinh_Phat took 48.383472204208374s
Availability | SPARQL endpoint availability check for gseg took 9.846687316894531e-05s
Availability | VoID file availability check for gseg took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for gseg took 0.2604827880859375s
Reputation | Calculation of the PageRank for gseg took 0.021408796310424805s
Interlinking | Calculation of Degree of Connection for gseg took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for gseg took 3.0994415283203125e-05s
Believability | Calculation of trust value for gseg took 6.67572021484375e-06s
INFO | --- Analysis for hongse took 3.1252403259277344s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.2887685298919678s
Availability | VoID file availability check for COURAGE Dataset took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.26770806312561035s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 2.9087066650390625e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 5.787645578384399s
Availability | SPARQL endpoint availability check for RoadTrb took 0.00010943412780761719s
Availability | VoID file availability check for RoadTrb took 0.001199960708618164s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.2603800296783447s
Reputation | Calculation of the PageRank for RoadTrb took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for RoadTrb took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 2.7894973754882812e-05s
Believability | Calculation of trust value for RoadTrb took 1.1682510375976562e-05s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.453465223312378s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0007803440093994141s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.27286529541015625s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.02089381217956543s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.9325485229492188e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 44.850942850112915s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 8.845329284667969e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.2626948356628418s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.0517578125e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.0967254638671875e-05s
INFO | --- Analysis for http:pakistan.com took 2.449387550354004s
Availability | SPARQL endpoint availability check for CEDICT took 8.749961853027344e-05s
Availability | VoID file availability check for CEDICT took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for CEDICT took 0.2674126625061035s
Reputation | Calculation of the PageRank for CEDICT took 0.02079296112060547s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.0994415283203125e-05s
Believability | Calculation of trust value for CEDICT took 6.318092346191406e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 3.796466588973999s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.3144218921661377s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.27004313468933105s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.022513389587402344s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.842613220214844e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0251998901367188e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 4.575445175170898s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 0.00011229515075683594s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.2686138153076172s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.021056175231933594s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.075599670410156e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 1.1205673217773438e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 2.992568254470825s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.744529724121094e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.27660274505615234s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.023122549057006836s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.266334533691406e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.1205673217773438e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.4311227798461914s
Availability | SPARQL endpoint availability check for Soccer Dataset took 8.797645568847656e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.26153016090393066s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 2.8371810913085938e-05s
Believability | Calculation of trust value for Soccer Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for http:www.msm.com took 2.4209036827087402s
Availability | SPARQL endpoint availability check for Game Ontology took 8.296966552734375e-05s
Availability | VoID file availability check for Game Ontology took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.2643907070159912s
Reputation | Calculation of the PageRank for Game Ontology took 0.02153635025024414s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.3855438232421875e-05s
Believability | Calculation of trust value for Game Ontology took 1.33514404296875e-05s
INFO | --- Analysis for http:www.RAG.comgameonto# took 3.0034148693084717s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.845329284667969e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.26810312271118164s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.021075963973999023s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.266334533691406e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.775161743164062e-06s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.001049757003784s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 9.107589721679688e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2728428840637207s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02199101448059082s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0009503364562988281s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.337860107421875e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.2159347534179688e-05s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.402543783187866s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.821487426757812e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2712361812591553s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02137613296508789s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.765655517578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1444091796875e-05s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.455566644668579s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.702278137207031e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.26911354064941406s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02303028106689453s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0279159545898438e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1682510375976562e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.477205991744995s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.560585021972656e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0010457038879394531s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2693610191345215s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.075599670410156e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.33514404296875e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.4235174655914307s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.749961853027344e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2731754779815674s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8848648071289062e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.0728836059570312e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 3.9548914432525635s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.00010085105895996094s
Availability | VoID file availability check for Indian Biodiversity took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2683897018432617s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02053046226501465s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0994415283203125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2159347534179688e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.4071388244628906s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 9.34600830078125e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.26619958877563477s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.021732807159423828s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 2.86102294921875e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.1920928955078125e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 4.3243231773376465s
Availability | SPARQL endpoint availability check for Bookkeeping took 0.9465501308441162s
Availability | VoID file availability check for Bookkeeping took 0.0006740093231201172s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.2724745273590088s
Reputation | Calculation of the PageRank for Bookkeeping took 0.02096414566040039s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 2.8848648071289062e-05s
Believability | Calculation of trust value for Bookkeeping took 1.2159347534179688e-05s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 3.8337132930755615s
Availability | SPARQL endpoint availability check for Legal Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Legal Ontology took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.2710249423980713s
Reputation | Calculation of the PageRank for Legal Ontology took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for Legal Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 2.9685323238372803s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 8.845329284667969e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2723531723022461s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020846128463745117s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.581710815429688e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.1920928955078125e-05s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.8384644985198975s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.291534423828125e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.30998730659484863s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.021323442459106445s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 3.0994415283203125e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 6.9141387939453125e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.7049129009246826s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 0.497661828994751s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.26258373260498047s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.0207517147064209s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010609626770019531s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 1.1205673217773438e-05s
INFO | --- Analysis for hungarian-national-library-catalog took 2.7986197471618652s
Availability | SPARQL endpoint availability check for IATE RDF took 0.00011014938354492188s
Availability | VoID file availability check for IATE RDF took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.26574039459228516s
Reputation | Calculation of the PageRank for IATE RDF took 0.020823955535888672s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.504753112792969e-05s
Believability | Calculation of trust value for IATE RDF took 1.0967254638671875e-05s
INFO | --- Analysis for iate-rdf took 2.642777919769287s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.011117458343506s
Availability | VoID file availability check for IATI as Linked Data took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.27143406867980957s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.249282836914062e-05s
Believability | Calculation of trust value for IATI as Linked Data took 1.239776611328125e-05s
INFO | --- Analysis for iati-as-linked-data took 12.753694295883179s
Availability | SPARQL endpoint availability check for ICANE took 0.2989373207092285s
Availability | VoID file availability check for ICANE took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for ICANE took 0.27083349227905273s
Reputation | Calculation of the PageRank for ICANE took 0.022515535354614258s
Interlinking | Calculation of Degree of Connection for ICANE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for ICANE took 9.298324584960938e-05s
Believability | Calculation of trust value for ICANE took 7.62939453125e-06s
INFO | --- Analysis for icane took 3.4522151947021484s
Availability | SPARQL endpoint availability check for ichoose took 0.14330840110778809s
Availability | VoID file availability check for ichoose took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for ichoose took 0.27124834060668945s
Reputation | Calculation of the PageRank for ichoose took 0.02076888084411621s
Interlinking | Calculation of Degree of Connection for ichoose took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ichoose took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.508827209472656e-05s
Believability | Calculation of trust value for ichoose took 1.0728836059570312e-05s
INFO | --- Analysis for ichoose took 40.143951654434204s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 0.6437556743621826s
Availability | VoID file availability check for The Iconology Dataset took 0.0005877017974853516s
Extra | Recovery of all triples for The Iconology Dataset took 3.8044326305389404s
Performance | Total latancy measurement for The Iconology Dataset took 0.4624345302581787s
Amount of data | Number of triples check for The Iconology Dataset took 0.16389751434326172s
Interoperability | New terms check for The Iconology Dataset took 1.318591594696045s
Versatility | Languages check for The Iconology Dataset took 0.567481279373169s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.18656206130981445s
Interpretability | RDF structures check for The Iconology Dataset took 0.12027621269226074s
Versatility | Serialization formats check for The Iconology Dataset took 0.10391569137573242s
Availability | RDF dump link check for The Iconology Dataset took 0.08348941802978516s
License | MR license check for The Iconology Dataset took 0.09420299530029297s
License | HR license check for The Iconology Dataset took 0.23940420150756836s
Amount of data | Number of property check for The Iconology Dataset took 0.09670233726501465s
Understandability | Number of label check for The Iconology Dataset took 0.13535428047180176s
Understandability | URI regex check for The Iconology Dataset took 0.16949105262756348s
Understandability | Vocabs check for The Iconology Dataset took 0.08683419227600098s
Verifiability | Authors check for The Iconology Dataset took 0.09197545051574707s
Verifiability | Publishers check for The Iconology Dataset took 0.08808565139770508s
Performance | Throughput check for The Iconology Dataset took 10.352882623672485s
Amount of data | Check the number of entities for The Iconology Dataset took 0.0005443096160888672s
Verifiability | Contribs. check for The Iconology Dataset took 0.07854223251342773s
Interlinking | sameAs chians check for The Iconology Dataset took 0.0746300220489502s
Interlinking | skos check for The Iconology Dataset took 0.08361196517944336s
Interlinking | skos check for The Iconology Dataset took 0.08428359031677246s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.08545732498168945s
Currency | Creation date check for The Iconology Dataset took 0.17270350456237793s
Currency | Modification date check for The Iconology Dataset took 0.18646621704101562s
Rep.Conc. | URIs length for The Iconology Dataset took 1.2281296253204346s
Interoperability | New vocabularies check for The Iconology Dataset took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.07621955871582031s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.24297165870666504s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.016223430633544922s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.41617417335510254s
Consistency | Disjoint class check for The Iconology Dataset took 0.07757282257080078s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.13784527778625488s
Consistency | Misplaced classes for The Iconology Dataset took 0.8281185626983643s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.4366142749786377s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.1297886371612549s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.2154607772827148s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.286588191986084s
Security | Sign check for The Iconology Dataset took 0.07833218574523926s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2568.245611190796s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 0.596968412399292s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.020915985107421875s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.621246337890625e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 9.5367431640625e-07s
Believability | Calculation of trust value for The Iconology Dataset took 1.2874603271484375e-05s
INFO | --- Analysis for iconology-dataset took 2622.496814966202s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.649162292480469e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0007424354553222656s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.27556800842285156s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02113819122314453s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 8.368492126464844e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 1.1920928955078125e-05s
INFO | --- Analysis for idreffr took 3.533064365386963s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 1.5742676258087158s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.277254581451416s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.02125835418701172s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 5.0067901611328125e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 9.298324584960938e-06s
INFO | --- Analysis for ids took 4.528030157089233s
Availability | SPARQL endpoint availability check for ietflang took 8.463859558105469e-05s
Availability | VoID file availability check for ietflang took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for ietflang took 0.27489495277404785s
Reputation | Calculation of the PageRank for ietflang took 0.022796630859375s
Interlinking | Calculation of Degree of Connection for ietflang took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.6253204345703125e-05s
Believability | Calculation of trust value for ietflang took 1.0728836059570312e-05s
INFO | --- Analysis for ietflang took 14.27677297592163s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.6041412353515625s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.28102684020996094s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02083134651184082s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.886222839355469e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.2874603271484375e-05s
INFO | --- Analysis for IGVLL took 4.115957260131836s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.4326481819152832s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.000682830810546875s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.2629168033599854s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.8854553699493408s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.19549298286437988s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.372450828552246s
Versatility | Languages check for 3LGM² IHE Ontology took 0.2019493579864502s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.17190074920654297s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.2042236328125s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.18570542335510254s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.17786312103271484s
License | MR license check for 3LGM² IHE Ontology took 0.1787726879119873s
License | HR license check for 3LGM² IHE Ontology took 0.19092249870300293s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.18138718605041504s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.19579386711120605s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.36012887954711914s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.17605304718017578s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.18332362174987793s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.18457841873168945s
Performance | Throughput check for 3LGM² IHE Ontology took 10.561781167984009s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 7.295608520507812e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.16933894157409668s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.17765212059020996s
Interlinking | skos check for 3LGM² IHE Ontology took 0.1799030303955078s
Interlinking | skos check for 3LGM² IHE Ontology took 0.16843509674072266s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.18032050132751465s
Currency | Creation date check for 3LGM² IHE Ontology took 0.36710119247436523s
Currency | Modification date check for 3LGM² IHE Ontology took 0.38613367080688477s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.7216510772705078s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.17885541915893555s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.18214988708496094s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.1695401668548584s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.3212101459503174s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.0034606456756591797s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.05301856994628906s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.23756909370422363s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.42318058013916016s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.2582669258117676s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.4696547985076904s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.1566228866577148s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.3976483345031738s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.031101465225219727s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.18403267860412598s
Security | Sign check for 3LGM² IHE Ontology took 0.17053866386413574s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 366.14602041244507s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.3222389221191406s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.021092891693115234s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 3.9577484130859375e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.430511474609375e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for IHE took 409.34656286239624s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 2.7747421264648438s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0008752346038818359s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 6.602844953536987s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 9.000739097595215s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 22.248607397079468s
Interoperability | New terms check for Test Site, LOD Lab 317 took 8.33095932006836s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.78755784034729s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 1.9688987731933594s
Security | Check HTTPS for Test Site, LOD Lab 317 took 1.195488452911377s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 1.9812977313995361s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.8992483615875244s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.8190665245056152s
License | MR license check for Test Site, LOD Lab 317 took 1.8641409873962402s
License | HR license check for Test Site, LOD Lab 317 took 2.164045572280884s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.8538172245025635s
Understandability | Number of label check for Test Site, LOD Lab 317 took 1.95871901512146s
Understandability | URI regex check for Test Site, LOD Lab 317 took 3.6062278747558594s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.8103466033935547s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.859527349472046s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 1.804272174835205s
Performance | Throughput check for Test Site, LOD Lab 317 took 17.937975883483887s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 9.059906005859375e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.8337631225585938s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.812312364578247s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.8551146984100342s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.8273241519927979s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.8454360961914062s
Currency | Creation date check for Test Site, LOD Lab 317 took 3.6563329696655273s
Currency | Modification date check for Test Site, LOD Lab 317 took 3.6370902061462402s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 34.893489837646484s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.8051366806030273s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.8036818504333496s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.7941882610321045s
Accuracy | Check Empty annotation labels for Test Site, LOD Lab 317 took 3.586235761642456s
Accuracy | Check White space in annotation for Test Site, LOD Lab 317 took 0.02982950210571289s
Accuracy | Check Datatype consistency for Test Site, LOD Lab 317 took 0.028756141662597656s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.7973337173461914s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 27.15853261947632s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 2.3823297023773193s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 11.141655445098877s
Consistency | Check Invalid usage of undefined classes for Test Site, LOD Lab 317 took 1.1636898517608643s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 23.946035623550415s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.035436153411865234s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.422142505645752s
Security | Sign check for Test Site, LOD Lab 317 took 1.8354320526123047s
Availability | Check URIs Dereferenciability for Test Site, LOD Lab 317 took 8.641211748123169s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.3066072463989258s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.021464109420776367s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 4.38690185546875e-05s
Interoperability | Check the re-using of existing vocabs for Test Site, LOD Lab 317 took 1.1920928955078125e-06s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 1.1444091796875e-05s
INFO | --- Analysis for iislod-test took 587.3682560920715s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.649162292480469e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0007195472717285156s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.26801490783691406s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.021612882614135742s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.218650817871094e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 1.1920928955078125e-05s
INFO | --- Analysis for ILUSOC took 18.20847201347351s
Availability | SPARQL endpoint availability check for im@sparql took 7.223659038543701s
Availability | VoID file availability check for im@sparql took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for im@sparql took 0.26789140701293945s
Reputation | Calculation of the PageRank for im@sparql took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.170967102050781e-05s
Believability | Calculation of trust value for im@sparql took 1.2159347534179688e-05s
INFO | --- Analysis for im@sparql took 14.816585063934326s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.38690185546875e-05s
Availability | VoID file availability check for imagery bailingniao took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.2680678367614746s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.022722721099853516s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.647804260253906e-05s
Believability | Calculation of trust value for imagery bailingniao took 5.9604644775390625e-06s
INFO | --- Analysis for imagery_bailingniao took 3.8588345050811768s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.0716781616210938s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0007653236389160156s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 19.562724113464355s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.364978790283203s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 10.07470965385437s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.433868408203125s
Versatility | Languages check for Imagesnippets Image Descriptions took 19.641988277435303s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.682203769683838s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.64548659324646s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.6874258518218994s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.6719181537628174s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.6891593933105469s
License | MR license check for Imagesnippets Image Descriptions took 0.6969759464263916s
License | HR license check for Imagesnippets Image Descriptions took 30.702956199645996s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.6839852333068848s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.6006813049316406s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.3460993766784668s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.6839666366577148s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7009906768798828s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.6750438213348389s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.359965562820435s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 7.128715515136719e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.702232837677002s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.6760263442993164s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6939840316772461s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6489639282226562s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.6764688491821289s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.3991236686706543s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.3738212585449219s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 32.546523332595825s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.6871557235717773s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7007498741149902s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.6777427196502686s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 11.054617166519165s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.1675355434417725s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.203322172164917s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.6877505779266357s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.806953430175781s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 4.688445568084717s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.2466022968292236s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.296268939971924s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 2.8018128871917725s
Security | Sign check for Imagesnippets Image Descriptions took 0.689547061920166s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 10.886596202850342s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.35715222358703613s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.02111506462097168s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.799003601074219e-05s
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.0013580322265625e-05s
INFO | --- Analysis for imagesnippets took 370.83323764801025s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.09007453918457031s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0004267692565917969s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.2639031410217285s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.022186756134033203s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.797645568847656e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for imf-linked-data took 2.6025450229644775s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.267692565917969e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.26344919204711914s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.021984338760375977s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.1682510375976562e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 1.0251998901367188e-05s
INFO | --- Analysis for Imtiaz took 2.452054738998413s
Availability | SPARQL endpoint availability check for Royalty Free Music took 8.416175842285156e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.2625877857208252s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.02131962776184082s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 3.147125244140625e-05s
Believability | Calculation of trust value for Royalty Free Music took 1.0013580322265625e-05s
INFO | --- Analysis for inaudio.org took 3.7879507541656494s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.5131688117980957s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.2658064365386963s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.022731304168701172s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.886222839355469e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 9.775161743164062e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 4.137998580932617s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 8.392333984375e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0007379055023193359s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.2700185775756836s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.021088361740112305s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00011348724365234375s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 1.2636184692382812e-05s
INFO | --- Analysis for ineverycrea took 18.897163152694702s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.702278137207031e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.26703667640686035s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.021062612533569336s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.942054748535156e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.1444091796875e-05s
INFO | --- Analysis for ineverycrea-argentina took 11.56973648071289s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 272.16477060317993s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0007402896881103516s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.2834804058074951s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02126598358154297s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 8.130073547363281e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for influence-tracker-dataset took 565.697918176651s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.2756936550140381s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020772695541381836s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.6716461181640625e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 1.2159347534179688e-05s
INFO | --- Analysis for instance-hub-fiscal-years took 2.462585210800171s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 8.535385131835938e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.2965097427368164s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.020776033401489258s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00010538101196289062s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.049041748046875e-05s
INFO | --- Analysis for interactivemaps-gnoss took 10.487890005111694s
Availability | SPARQL endpoint availability check for intervalue took 0.12370705604553223s
Availability | VoID file availability check for intervalue took 0.00020384788513183594s
Completeness | Calculation of interlinking completeness for intervalue took 0.2622983455657959s
Reputation | Calculation of the PageRank for intervalue took 0.020862102508544922s
Interlinking | Calculation of Degree of Connection for intervalue took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.985664367675781e-05s
Believability | Calculation of trust value for intervalue took 1.1205673217773438e-05s
INFO | --- Analysis for intervalue took 2.653076171875s
Availability | SPARQL endpoint availability check for Inztrow took 4.100799560546875e-05s
Availability | VoID file availability check for Inztrow took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Inztrow took 0.27158117294311523s
Reputation | Calculation of the PageRank for Inztrow took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Inztrow took 2.9087066650390625e-05s
Believability | Calculation of trust value for Inztrow took 1.0251998901367188e-05s
INFO | --- Analysis for Inztrow took 3.7393710613250732s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.28575563430786133s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.020404577255249023s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 2.8848648071289062e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for ipbes took 3.7778165340423584s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 8.916854858398438e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.2633211612701416s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.020513057708740234s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.076957702636719e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 1.0251998901367188e-05s
INFO | --- Analysis for iptc-newscodes took 3.1886398792266846s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 1.6531329154968262s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.2676568031311035s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.703636169433594e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 1.0967254638671875e-05s
INFO | --- Analysis for iserve took 6.406606674194336s
Availability | SPARQL endpoint availability check for ISIC V4 took 21.271962642669678s
Availability | VoID file availability check for ISIC V4 took 0.0007877349853515625s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.29549312591552734s
Reputation | Calculation of the PageRank for ISIC V4 took 0.02148270606994629s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 4.00543212890625e-05s
Believability | Calculation of trust value for ISIC V4 took 9.059906005859375e-06s
INFO | --- Analysis for isic-v4 took 114.64556407928467s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.3392181396484375e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.30473923683166504s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.022225618362426758s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 6.628036499023438e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 8.58306884765625e-06s
INFO | --- Analysis for isil-dbpedia took 4.222323417663574s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.315376281738281e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.2776460647583008s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.022786855697631836s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.4332275390625e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 1.1920928955078125e-05s
INFO | --- Analysis for iso-639-oasis took 3.0703916549682617s
Availability | SPARQL endpoint availability check for ISOcat took 8.893013000488281e-05s
Availability | VoID file availability check for ISOcat took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for ISOcat took 0.3055245876312256s
Reputation | Calculation of the PageRank for ISOcat took 0.020841360092163086s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.008148193359375e-05s
Believability | Calculation of trust value for ISOcat took 1.049041748046875e-05s
INFO | --- Analysis for isocat took 33.26153016090393s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.291534423828125e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.2876577377319336s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020996809005737305s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.528594970703125e-05s
Believability | Calculation of trust value for ISOcat-metadata took 9.775161743164062e-06s
INFO | --- Analysis for isocat-metadata took 32.66631078720093s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13809442520141602s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0005526542663574219s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.390050649642944s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.27610349655151367s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1312239170074463s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.8056764602661133s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.71086096763611s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0813913345336914s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.45302724838256836s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1005859375s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0919656753540039s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08625316619873047s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13869953155517578s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.9800295829773s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08140015602111816s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3287179470062256s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.31189489364624023s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12683391571044922s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12332987785339355s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07751774787902832s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.268758058547974s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.2479248046875e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12433671951293945s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19612908363342285s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.424727201461792s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.41712450981140137s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12777447700500488s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16635894775390625s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07592535018920898s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 13.003750801086426s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09986209869384766s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07967138290405273s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0815422534942627s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.7048070430755615s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3061995506286621s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.25896453857421875s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07153034210205078s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.11730432510376s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.8991031646728516s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.6436071395874023s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1447570323944092s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.41325306892395s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2904791831970215s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08612966537475586s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09816384315490723s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.59256100654602s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.31340503692626953s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0212099552154541s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00010442733764648438s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.9073486328125e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2159347534179688e-05s
INFO | --- Analysis for ispra-lod-place took 448.96586990356445s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.05885004997253418s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0003190040588378906s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 5.41916298866272s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.2589724063873291s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.1422274112701416s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.8060710430145264s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 91.11338090896606s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.07721662521362305s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.02996373176574707s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.10622191429138184s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.08955001831054688s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.07665657997131348s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.14176034927368164s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 91.10589456558228s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.08414435386657715s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.4071383476257324s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.304126501083374s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.12844014167785645s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.13940763473510742s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.07569718360900879s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.307117223739624s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 7.033348083496094e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.14017987251281738s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.22208404541015625s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.5157973766326904s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.48659682273864746s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.13625168800354004s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.15308809280395508s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.07555699348449707s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 12.895065784454346s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 6.67572021484375e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.08446741104125977s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.07991409301757812s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.08620333671569824s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 2.987090826034546s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.3047924041748047s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.26758480072021484s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.07159852981567383s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.046176671981812s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.8845911026000977s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 2.8004298210144043s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.205479621887207s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.002842426300049s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.29122281074523926s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.08160829544067383s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.09856033325195312s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 8.273192405700684s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.36151885986328125s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.021343231201171875s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 1.2636184692382812e-05s
INFO | --- Analysis for ispra-lod-ron took 441.2441146373749s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.5943682193756104s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.27018308639526367s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.021489858627319336s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.441375732421875e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for issa-agritrop took 4.595845937728882s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.458427429199219e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2769653797149658s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020916223526000977s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.1948089599609375e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 6.9141387939453125e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.4215714931488037s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.506111145019531e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.28021883964538574s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020932912826538086s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.0994415283203125e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.6450881958007812e-05s
INFO | --- Analysis for ISSN:_0080-3626 took 2.727828025817871s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.267692565917969e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.2750859260559082s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0009691715240478516s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.814697265625e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 1.2159347534179688e-05s
INFO | --- Analysis for ISSN:_0080-3626. took 2.5903480052948s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 0.26969218254089355s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.267838716506958s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.021472454071044922s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.20159912109375e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 9.298324584960938e-06s
INFO | --- Analysis for istat-immigration took 2.7508373260498047s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.24343371391296387s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0007936954498291016s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.2698831558227539s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020835399627685547s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0009136199951171875s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.504753112792969e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 1.0251998901367188e-05s
INFO | --- Analysis for it-aifa-drug-prices took 2.917518138885498s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 0.2154698371887207s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.2699160575866699s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.02182173728942871s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 6.866455078125e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 1.1205673217773438e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 2.6690850257873535s
Availability | SPARQL endpoint availability check for IWN took 8.940696716308594e-05s
Availability | VoID file availability check for IWN took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for IWN took 0.2968018054962158s
Reputation | Calculation of the PageRank for IWN took 0.022695302963256836s
Interlinking | Calculation of Degree of Connection for IWN took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for IWN took 3.6716461181640625e-05s
Believability | Calculation of trust value for IWN took 1.049041748046875e-05s
INFO | --- Analysis for iwn took 5.944561719894409s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 5.698241710662842s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.26410651206970215s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.02110433578491211s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.341934204101562e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 1.049041748046875e-05s
INFO | --- Analysis for jamendo-dbtune took 9.87243103981018s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 8.893013000488281e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0006928443908691406s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.2680377960205078s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020758628845214844s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 5.340576171875e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.613985061645508s
Availability | SPARQL endpoint availability check for JEL Classification took 8.463859558105469e-05s
Availability | VoID file availability check for JEL Classification took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2755300998687744s
Reputation | Calculation of the PageRank for JEL Classification took 0.021350622177124023s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.075599670410156e-05s
Believability | Calculation of trust value for JEL Classification took 1.0013580322265625e-05s
INFO | --- Analysis for jel-classification took 4.62060022354126s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.1136932373046875s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0003821849822998047s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.29979801177978516s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.02103137969970703s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.1948089599609375e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 7.62939453125e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 7.362597942352295s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.39640402793884s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.27015113830566406s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.02144908905029297s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.843971252441406e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.0967254638671875e-05s
INFO | --- Analysis for jita took 542.2635827064514s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.062330961227417s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.29228639602661133s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.020983219146728516s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 9.1552734375e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.0967254638671875e-05s
INFO | --- Analysis for john-goodwins-family-tree took 62.833611726760864s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 8.535385131835938e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.2713131904602051s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.02231740951538086s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 4.100799560546875e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 1.0728836059570312e-05s
INFO | --- Analysis for jp-cos took 4.526284217834473s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 9.918212890625e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.2689015865325928s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.02085709571838379s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 4.0531158447265625e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 1.52587890625e-05s
INFO | --- Analysis for jp-textbook took 4.167055368423462s
Availability | SPARQL endpoint availability check for JRC-Names took 4.315376281738281e-05s
Availability | VoID file availability check for JRC-Names took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.2780280113220215s
Reputation | Calculation of the PageRank for JRC-Names took 0.021281003952026367s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.552436828613281e-05s
Believability | Calculation of trust value for JRC-Names took 1.1444091796875e-05s
INFO | --- Analysis for jrc-names-ec took 4.498518466949463s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.6295099258422852s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.268749475479126s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.02081775665283203s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.794929504394531e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 1.1444091796875e-05s
INFO | --- Analysis for jrc-names-mlode took 4.252233982086182s
Availability | SPARQL endpoint availability check for JudaicaLink took 9.465217590332031e-05s
Availability | VoID file availability check for JudaicaLink took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.2820265293121338s
Reputation | Calculation of the PageRank for JudaicaLink took 0.02085733413696289s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00010061264038085938s
Believability | Calculation of trust value for JudaicaLink took 1.1205673217773438e-05s
INFO | --- Analysis for judaicalink took 4.263921022415161s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.05633401870727539s
Availability | VoID file availability check for Kallikratis municipalities took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.2653019428253174s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.202957153320312e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 8.106231689453125e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.563873767852783s
Availability | SPARQL endpoint availability check for EU Soccer League took 4.291534423828125e-05s
Availability | VoID file availability check for EU Soccer League took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.26351237297058105s
Reputation | Calculation of the PageRank for EU Soccer League took 0.022154808044433594s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.0517578125e-05s
Believability | Calculation of trust value for EU Soccer League took 1.0251998901367188e-05s
INFO | --- Analysis for KG:Course_Submission took 3.8656556606292725s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 8.916854858398438e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.00048828125s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.27630019187927246s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.022652626037597656s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.239776611328125e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 1.0728836059570312e-05s
INFO | --- Analysis for KING took 2.675779342651367s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 8.463859558105469e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.29076433181762695s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.022117137908935547s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.532669067382812e-05s
Believability | Calculation of trust value for Klappstuhlclub took 7.62939453125e-06s
INFO | --- Analysis for klappstuhlclub took 12.547616720199585s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.858076572418213s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.27814602851867676s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.021768569946289062s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.67572021484375e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 1.0251998901367188e-05s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.370205640792847s
Availability | SPARQL endpoint availability check for Knowledge Forest took 8.368492126464844e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.27260756492614746s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.021211624145507812s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.218650817871094e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.0728836059570312e-05s
INFO | --- Analysis for KnowledgeFusion took 2.4638330936431885s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 8.749961853027344e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.2716960906982422s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.02365851402282715s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0009801387786865234s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 8.702278137207031e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 1.0967254638671875e-05s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.093283891677856s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.4345855712890625e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.2744264602661133s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020783662796020508s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 2.9087066650390625e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.298324584960938e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.4721274375915527s
Availability | SPARQL endpoint availability check for Informatics Studies took 8.392333984375e-05s
Availability | VoID file availability check for Informatics Studies took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.2934608459472656s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020318269729614258s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 3.8623809814453125e-05s
Believability | Calculation of trust value for Informatics Studies took 9.298324584960938e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 2.987377166748047s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.19701147079467773s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0007486343383789062s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2770974636077881s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.021021366119384766s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.790855407714844e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 2.574920654296875e-05s
INFO | --- Analysis for kupkb took 9.614535331726074s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 8.835580348968506s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.2864046096801758s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020735979080200195s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.963180541992188e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 1.0967254638671875e-05s
INFO | --- Analysis for l3s-dblp took 43.17495679855347s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 23.77907657623291s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.2815582752227783s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.021138906478881836s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.461143493652344e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for lak-dataset took 66.87466287612915s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.1875166893005371s
Availability | VoID file availability check for  Language Name Authority List  took 0.0004639625549316406s
Extra | Recovery of all triples for  Language Name Authority List  took 162.19953274726868s
Performance | Total latancy measurement for  Language Name Authority List  took 0.5741593837738037s
Amount of data | Number of triples check for  Language Name Authority List  took 50.948209047317505s
Interoperability | New terms check for  Language Name Authority List  took 60.63933610916138s
Versatility | Languages check for  Language Name Authority List  took 300.12105417251587s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 16.304444551467896s
Security | Check HTTPS for  Language Name Authority List  took 0.3163015842437744s
Interpretability | RDF structures check for  Language Name Authority List  took 0.2533109188079834s
Versatility | Serialization formats check for  Language Name Authority List  took 4.391284227371216s
Availability | RDF dump link check for  Language Name Authority List  took 0.24959135055541992s
License | MR license check for  Language Name Authority List  took 0.5151808261871338s
License | HR license check for  Language Name Authority List  took 300.1041293144226s
Amount of data | Number of property check for  Language Name Authority List  took 0.15636897087097168s
Understandability | Number of label check for  Language Name Authority List  took 2.8505187034606934s
Understandability | URI regex check for  Language Name Authority List  took 0.3825058937072754s
Understandability | Vocabs check for  Language Name Authority List  took 0.14045071601867676s
Verifiability | Authors check for  Language Name Authority List  took 0.24953532218933105s
Verifiability | Publishers check for  Language Name Authority List  took 0.21273541450500488s
Performance | Throughput check for  Language Name Authority List  took 10.887730836868286s
Amount of data | Check the number of entities for  Language Name Authority List  took 6.794929504394531e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.16799354553222656s
Interlinking | sameAs chians check for  Language Name Authority List  took 9.546359539031982s
Interlinking | skos check for  Language Name Authority List  took 0.18361115455627441s
Interlinking | skos check for  Language Name Authority List  took 0.2932555675506592s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.26096272468566895s
Currency | Creation date check for  Language Name Authority List  took 0.3148484230041504s
Currency | Modification date check for  Language Name Authority List  took 0.19551897048950195s
Rep.Conc. | URIs length for  Language Name Authority List  took 418.24419045448303s
Interoperability | New vocabularies check for  Language Name Authority List  took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.14989900588989258s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.1810157299041748s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.16053414344787598s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 39.612011194229126s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.159081220626831s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.597332715988159s
Consistency | Disjoint class check for  Language Name Authority List  took 0.16110777854919434s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.43586015701294s
Consistency | Misplaced classes for  Language Name Authority List  took 8.312380313873291s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 40.58086085319519s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.4174177646636963s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.27578139305115s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 2.9417004585266113s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.3630657196044922s
Security | Sign check for  Language Name Authority List  took 0.4078257083892822s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 11.274012088775635s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 0.6089951992034912s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.021421432495117188s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 0.00010371208190917969s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.430511474609375e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 7.152557373046875e-06s
INFO | --- Analysis for language-authority-list took 14590.727324962616s
Availability | SPARQL endpoint availability check for Lark took 384.0865330696106s
Availability | VoID file availability check for Lark took 0.0008327960968017578s
Completeness | Calculation of interlinking completeness for Lark took 0.31979799270629883s
Reputation | Calculation of the PageRank for Lark took 0.022305727005004883s
Interlinking | Calculation of Degree of Connection for Lark took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Lark took 7.724761962890625e-05s
Believability | Calculation of trust value for Lark took 1.0728836059570312e-05s
INFO | --- Analysis for LARK took 1675.3689858913422s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.4234006404876709s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.26262855529785156s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020958423614501953s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 4.506111145019531e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for LASLA took 3.9450931549072266s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.40903472900390625s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.267014741897583s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.0213470458984375s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 2.86102294921875e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 4.100799560546875e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 1.0967254638671875e-05s
INFO | --- Analysis for Latin_Vallex2.0 took 4.031718015670776s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.39641618728637695s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.2923774719238281s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.021113157272338867s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.886222839355469e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 8.821487426757812e-06s
INFO | --- Analysis for LatinAffectus took 4.065264701843262s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.39534592628479004s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.26769399642944336s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.021818876266479492s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.363059997558594e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 1.3828277587890625e-05s
INFO | --- Analysis for LatinWordnetLiLa took 3.95930552482605s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 8.606910705566406e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.27270936965942383s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.0211794376373291s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011920928955078125s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.2636184692382812e-05s
INFO | --- Analysis for lcsh took 7.439320802688599s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 8.678436279296875e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.27165651321411133s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.02083563804626465s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.416175842285156e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 1.1205673217773438e-05s
INFO | --- Analysis for lcsubjects took 2.6729254722595215s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.562966585159302s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.000774383544921875s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.3266892433166504s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.02195429801940918s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.863739013671875e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.2159347534179688e-05s
INFO | --- Analysis for ldt@library took 35.6827929019928s
Availability | SPARQL endpoint availability check for U ime Legije took 9.012222290039062e-05s
Availability | VoID file availability check for U ime Legije took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.2670624256134033s
Reputation | Calculation of the PageRank for U ime Legije took 0.021168231964111328s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.5762786865234375e-05s
Believability | Calculation of trust value for U ime Legije took 1.0728836059570312e-05s
INFO | --- Analysis for LEGIJA_STRANACA took 2.4130747318267822s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.399212121963501s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0007672309875488281s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.27129244804382324s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.021103382110595703s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.2479248046875e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.2159347534179688e-05s
INFO | --- Analysis for LemmaBank took 4.227388381958008s
Availability | SPARQL endpoint availability check for lemonUby took 8.58306884765625e-05s
Availability | VoID file availability check for lemonUby took 0.0013670921325683594s
Completeness | Calculation of interlinking completeness for lemonUby took 0.2745201587677002s
Reputation | Calculation of the PageRank for lemonUby took 0.020850419998168945s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.604194641113281e-05s
Believability | Calculation of trust value for lemonUby took 1.2159347534179688e-05s
INFO | --- Analysis for lemonuby took 3.4170455932617188s
Availability | SPARQL endpoint availability check for LemonWiktionary took 8.654594421386719e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.27692556381225586s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.02143692970275879s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0009636878967285156s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 4.601478576660156e-05s
Believability | Calculation of trust value for LemonWiktionary took 1.2159347534179688e-05s
INFO | --- Analysis for lemonwiktionary took 4.273571014404297s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.38913416862487793s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.2939579486846924s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.021088600158691406s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.981590270996094e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for LewisShort took 3.900315284729004s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 0.9326839447021484s
Availability | VoID file availability check for LEXIN-RDF took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.28997111320495605s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.02081441879272461s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.218650817871094e-05s
Believability | Calculation of trust value for LEXIN-RDF took 1.239776611328125e-05s
INFO | --- Analysis for lexin-rdf took 5.483369827270508s
Availability | SPARQL endpoint availability check for lexinfo took 8.535385131835938e-05s
Availability | VoID file availability check for lexinfo took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for lexinfo took 0.2625868320465088s
Reputation | Calculation of the PageRank for lexinfo took 0.02115488052368164s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.96453857421875e-05s
Believability | Calculation of trust value for lexinfo took 1.1920928955078125e-05s
INFO | --- Analysis for lexinfo took 2.8030152320861816s
Availability | SPARQL endpoint availability check for Lexvo took 9.989738464355469e-05s
Availability | VoID file availability check for Lexvo took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for Lexvo took 0.2723877429962158s
Reputation | Calculation of the PageRank for Lexvo took 0.02101755142211914s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017261505126953125s
Believability | Calculation of trust value for Lexvo took 1.1682510375976562e-05s
INFO | --- Analysis for lexvo took 3.0223917961120605s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.363059997558594e-05s
Availability | VoID file availability check for Lexvo.org took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.26293134689331055s
Reputation | Calculation of the PageRank for Lexvo.org took 0.020711898803710938s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.796287536621094e-05s
Believability | Calculation of trust value for Lexvo.org took 1.1682510375976562e-05s
INFO | --- Analysis for lexvo-org took 2.5723648071289062s
Availability | SPARQL endpoint availability check for LIBRIS took 0.3572719097137451s
Availability | VoID file availability check for LIBRIS took 0.0005543231964111328s
Extra | Recovery of all triples for LIBRIS took 6.5139853954315186s
Performance | Total latancy measurement for LIBRIS took 0.6837542057037354s
Amount of data | Number of triples check for LIBRIS took 19.150432109832764s
Interoperability | New terms check for LIBRIS took 15.15071415901184s
Versatility | Languages check for LIBRIS took 0.17133855819702148s
Interpretability | Number of blank nodes check for LIBRIS took 300.09471583366394s
Security | Check HTTPS for LIBRIS took 0.324596643447876s
Interpretability | RDF structures check for LIBRIS took 0.39961695671081543s
Versatility | Serialization formats check for LIBRIS took 0.2129979133605957s
Availability | RDF dump link check for LIBRIS took 0.12950801849365234s
License | MR license check for LIBRIS took 0.23924565315246582s
License | HR license check for LIBRIS took 0.29465603828430176s
Amount of data | Number of property check for LIBRIS took 0.20011496543884277s
Understandability | Number of label check for LIBRIS took 0.5937070846557617s
Understandability | URI regex check for LIBRIS took 0.3927161693572998s
Understandability | Vocabs check for LIBRIS took 0.1315610408782959s
Verifiability | Authors check for LIBRIS took 0.1559295654296875s
Verifiability | Publishers check for LIBRIS took 0.14956235885620117s
Performance | Throughput check for LIBRIS took 10.374631881713867s
Amount of data | Check the number of entities for LIBRIS took 7.271766662597656e-05s
Verifiability | Contribs. check for LIBRIS took 0.1498394012451172s
Interlinking | sameAs chians check for LIBRIS took 0.21903681755065918s
Interlinking | skos check for LIBRIS took 0.4021778106689453s
Interlinking | skos check for LIBRIS took 0.1265277862548828s
Timeliness | dataset update frequency check for LIBRIS took 0.13307476043701172s
Currency | Creation date check for LIBRIS took 0.9637372493743896s
Currency | Modification date check for LIBRIS took 0.6772122383117676s
Rep.Conc. | URIs length for LIBRIS took 83.62799048423767s
Interoperability | New vocabularies check for LIBRIS took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.1726067066192627s
Accuracy | Check Functional Property for LIBRIS took 0.24269485473632812s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.18905210494995117s
Accuracy | Check Datatype consistency for LIBRIS took 0.27117037773132324s
Consistency | Disjoint class check for LIBRIS took 0.17099452018737793s
Consistency | Check Misplaced properties for LIBRIS took 60.60413146018982s
Consistency | Misplaced classes for LIBRIS took 1.0983750820159912s
Consistency | Check Ontology hijacking for LIBRIS took 3.3324246406555176s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.1636204719543457s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 61.524582624435425s
Conciseness | Check Extensional conciseness for LIBRIS took 0.27852797508239746s
Conciseness | Check Intensional conciseness for LIBRIS took 0.3731801509857178s
Security | Sign check for LIBRIS took 0.24392986297607422s
Availability | Check URIs Dereferenciability for LIBRIS took 10.15876579284668s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.3597586154937744s
Reputation | Calculation of the PageRank for LIBRIS took 0.020824909210205078s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 9.918212890625e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.430511474609375e-06s
Believability | Calculation of trust value for LIBRIS took 1.3589859008789062e-05s
INFO | --- Analysis for libris took 1052.7601561546326s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.13523292541503906s
Availability | VoID file availability check for Public Library of Veroia took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.27440309524536133s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.021104097366333008s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.867813110351562e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.1444091796875e-05s
INFO | --- Analysis for libver took 3.600120782852173s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.12045025825500488s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.2612876892089844s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.021196603775024414s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.177757263183594e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 8.106231689453125e-06s
INFO | --- Analysis for lichfield-spending took 2.5990023612976074s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 8.893013000488281e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.2757744789123535s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.02179861068725586s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.3855438232421875e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.0251998901367188e-05s
INFO | --- Analysis for lime took 7.225435256958008s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 8.654594421386719e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.45558786392211914s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.26849889755249023s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.02147221565246582s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010633468627929688s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.0013580322265625e-05s
INFO | --- Analysis for lingvoj took 5.925825119018555s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 8.678436279296875e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.2683858871459961s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.0209958553314209s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 9.131431579589844e-05s
Believability | Calculation of trust value for Linked Crunchbase took 1.0728836059570312e-05s
INFO | --- Analysis for linked-crunchbase took 14.907044887542725s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.3365929126739502s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.28761863708496094s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.023117780685424805s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.271766662597656e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1205673217773438e-05s
INFO | --- Analysis for linked-drugs took 6.521138906478882s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 8.821487426757812e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.2718689441680908s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.02110457420349121s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.822845458984375e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 8.344650268554688e-06s
INFO | --- Analysis for linked-edgar took 4.047247648239136s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.27161192893981934s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.02090740203857422s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.72747802734375e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 1.0013580322265625e-05s
INFO | --- Analysis for linked-eurostat took 3.4057223796844482s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.553794860839844e-05s
Availability | VoID file availability check for linked hypernyms took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.2652885913848877s
Reputation | Calculation of the PageRank for linked hypernyms took 0.02263474464416504s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.677078247070312e-05s
Believability | Calculation of trust value for linked hypernyms took 1.4066696166992188e-05s
INFO | --- Analysis for linked-hypernyms took 3.2919251918792725s
Availability | SPARQL endpoint availability check for Linked Life Data took 238.77565598487854s
Availability | VoID file availability check for Linked Life Data took 0.0007262229919433594s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.476743221282959s
Reputation | Calculation of the PageRank for Linked Life Data took 0.02365899085998535s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.001003265380859375s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 5.888938903808594e-05s
Believability | Calculation of trust value for Linked Life Data took 1.1444091796875e-05s
INFO | --- Analysis for linked-life-data took 682.1105391979218s
Availability | SPARQL endpoint availability check for Linked Logainm took 1.8774471282958984s
Availability | VoID file availability check for Linked Logainm took 0.0005822181701660156s
Extra | Recovery of all triples for Linked Logainm took 2.5619120597839355s
Performance | Total latancy measurement for Linked Logainm took 0.5376846790313721s
Amount of data | Number of triples check for Linked Logainm took 0.15477514266967773s
Interoperability | New terms check for Linked Logainm took 1.3087153434753418s
Versatility | Languages check for Linked Logainm took 1.4356443881988525s
Interpretability | Number of blank nodes check for Linked Logainm took 0.1297159194946289s
Security | Check HTTPS for Linked Logainm took 0.2494962215423584s
Interpretability | RDF structures check for Linked Logainm took 0.2471613883972168s
Versatility | Serialization formats check for Linked Logainm took 0.14128637313842773s
Availability | RDF dump link check for Linked Logainm took 0.1063082218170166s
License | MR license check for Linked Logainm took 0.12229061126708984s
License | HR license check for Linked Logainm took 0.11596274375915527s
Amount of data | Number of property check for Linked Logainm took 0.13223910331726074s
Understandability | Number of label check for Linked Logainm took 0.18691325187683105s
Understandability | URI regex check for Linked Logainm took 0.22171926498413086s
Understandability | Vocabs check for Linked Logainm took 0.10776901245117188s
Verifiability | Authors check for Linked Logainm took 0.11204695701599121s
Verifiability | Publishers check for Linked Logainm took 0.10863327980041504s
Performance | Throughput check for Linked Logainm took 10.424521684646606s
Amount of data | Check the number of entities for Linked Logainm took 7.677078247070312e-05s
Verifiability | Contribs. check for Linked Logainm took 0.11345267295837402s
Interlinking | sameAs chians check for Linked Logainm took 0.13426923751831055s
Interlinking | skos check for Linked Logainm took 0.14567160606384277s
Interlinking | skos check for Linked Logainm took 0.10605740547180176s
Timeliness | dataset update frequency check for Linked Logainm took 0.11819815635681152s
Currency | Creation date check for Linked Logainm took 0.24062108993530273s
Currency | Modification date check for Linked Logainm took 0.24184346199035645s
Rep.Conc. | URIs length for Linked Logainm took 0.9321098327636719s
Interoperability | New vocabularies check for Linked Logainm took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.12906455993652344s
Accuracy | Check Functional Property for Linked Logainm took 1.2215821743011475s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.18685436248779297s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.6350216865539551s
Accuracy | Check White space in annotation for Linked Logainm took 0.024063825607299805s
Accuracy | Check Datatype consistency for Linked Logainm took 0.0278017520904541s
Consistency | Disjoint class check for Linked Logainm took 0.18602323532104492s
Consistency | Check Misplaced properties for Linked Logainm took 0.30853724479675293s
Consistency | Misplaced classes for Linked Logainm took 0.26360034942626953s
Consistency | Check Ontology hijacking for Linked Logainm took 2.158693313598633s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.1266939640045166s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.31111741065979s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.032042503356933594s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.18721342086791992s
Security | Sign check for Linked Logainm took 0.11826109886169434s
Availability | Check URIs Dereferenciability for Linked Logainm took 938.7238910198212s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.3437983989715576s
Reputation | Calculation of the PageRank for Linked Logainm took 0.021633386611938477s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 8.96453857421875e-05s
Interoperability | Check the re-using of existing vocabs for Linked Logainm took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Logainm took 1.1920928955078125e-05s
INFO | --- Analysis for linked-logainm took 999.649649143219s
Availability | SPARQL endpoint availability check for Linked NUTS took 8.845329284667969e-05s
Availability | VoID file availability check for Linked NUTS took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.26244521141052246s
Reputation | Calculation of the PageRank for Linked NUTS took 0.02135920524597168s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.1975250244140625e-05s
Believability | Calculation of trust value for Linked NUTS took 8.821487426757812e-06s
INFO | --- Analysis for linked-nuts took 2.5149126052856445s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 0.35577917098999023s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.2698795795440674s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.02089214324951172s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 8.58306884765625e-06s
INFO | --- Analysis for linked-open-camera took 2.9322407245635986s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.3570027351379395s
Availability | VoID file availability check for Linked Open Commerce took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.29120945930480957s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.020664691925048828s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.0040740966796875e-05s
Believability | Calculation of trust value for Linked Open Commerce took 1.0728836059570312e-05s
INFO | --- Analysis for linked-open-commerce took 14.4536714553833s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 0.638787031173706s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.27322912216186523s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.0210723876953125s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 9.870529174804688e-05s
Believability | Calculation of trust value for Linked Open Data of Ecology took 1.1444091796875e-05s
INFO | --- Analysis for linked-open-data-of-ecology took 3.1519775390625s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 8.559226989746094e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.2618143558502197s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.02301955223083496s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.7738037109375e-05s
Believability | Calculation of trust value for Linked Open Numbers took 1.1444091796875e-05s
INFO | --- Analysis for linked-open-numbers took 2.6398026943206787s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.2721116542816162s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.02212381362915039s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.8848648071289062e-05s
Believability | Calculation of trust value for Linked Open Piracy took 9.298324584960938e-06s
INFO | --- Analysis for linked-open-piracy took 6.826171875s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 4.414217472076416s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0005950927734375s
Extra | Recovery of all triples for Linked Open Vocabularies (LOV) took 53.60079622268677s
Performance | Total latancy measurement for Linked Open Vocabularies (LOV) took 3.1297643184661865s
Amount of data | Number of triples check for Linked Open Vocabularies (LOV) took 1.4772210121154785s
Interoperability | New terms check for Linked Open Vocabularies (LOV) took 2.040414571762085s
Versatility | Languages check for Linked Open Vocabularies (LOV) took 13.400478601455688s
Interpretability | Number of blank nodes check for Linked Open Vocabularies (LOV) took 1.815539836883545s
Interpretability | RDF structures check for Linked Open Vocabularies (LOV) took 0.19942426681518555s
Versatility | Serialization formats check for Linked Open Vocabularies (LOV) took 0.1976454257965088s
Availability | RDF dump link check for Linked Open Vocabularies (LOV) took 0.9636232852935791s
License | MR license check for Linked Open Vocabularies (LOV) took 0.19468355178833008s
License | HR license check for Linked Open Vocabularies (LOV) took 81.64733648300171s
Amount of data | Number of property check for Linked Open Vocabularies (LOV) took 0.22475862503051758s
Understandability | Number of label check for Linked Open Vocabularies (LOV) took 0.7415883541107178s
Understandability | URI regex check for Linked Open Vocabularies (LOV) took 0.35193419456481934s
Understandability | Vocabs check for Linked Open Vocabularies (LOV) took 0.18901991844177246s
Verifiability | Authors check for Linked Open Vocabularies (LOV) took 0.20364618301391602s
Verifiability | Publishers check for Linked Open Vocabularies (LOV) took 0.21562671661376953s
Performance | Throughput check for Linked Open Vocabularies (LOV) took 91.77830266952515s
Amount of data | Check the number of entities for Linked Open Vocabularies (LOV) took 1.0595331192016602s
Verifiability | Contribs. check for Linked Open Vocabularies (LOV) took 0.8779757022857666s
Interlinking | sameAs chians check for Linked Open Vocabularies (LOV) took 0.2039804458618164s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.19000768661499023s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.1708230972290039s
Timeliness | dataset update frequency check for Linked Open Vocabularies (LOV) took 0.20025992393493652s
Currency | Creation date check for Linked Open Vocabularies (LOV) took 1.3406836986541748s
Currency | Modification date check for Linked Open Vocabularies (LOV) took 0.1847379207611084s
Rep.Conc. | URIs length for Linked Open Vocabularies (LOV) took 21.251238346099854s
Interoperability | New vocabularies check for Linked Open Vocabularies (LOV) took 505.0404646396637s
Consistency | Deprecated classes/propertiers check for Linked Open Vocabularies (LOV) took 0.22726893424987793s
Accuracy | Check Functional Property for Linked Open Vocabularies (LOV) took 0.18098974227905273s
Accuracy | Check Inverse Functional Property for Linked Open Vocabularies (LOV) took 0.2688734531402588s
Accuracy | Check Empty annotation labels for Linked Open Vocabularies (LOV) took 6.90953803062439s
Accuracy | Check White space in annotation for Linked Open Vocabularies (LOV) took 0.6839296817779541s
Accuracy | Check Datatype consistency for Linked Open Vocabularies (LOV) took 4.723209381103516s
Consistency | Disjoint class check for Linked Open Vocabularies (LOV) took 0.2147808074951172s
Consistency | Check Misplaced properties for Linked Open Vocabularies (LOV) took 6.212940216064453s
Consistency | Misplaced classes for Linked Open Vocabularies (LOV) took 0.2587904930114746s
Consistency | Check Ontology hijacking for Linked Open Vocabularies (LOV) took 51.15355205535889s
Consistency | Check Invalid usage of undefined classes for Linked Open Vocabularies (LOV) took 1.2124552726745605s
Conciseness | Check Extensional conciseness for Linked Open Vocabularies (LOV) took 2.813208818435669s
Conciseness | Check Intensional conciseness for Linked Open Vocabularies (LOV) took 15.22825002670288s
Security | Sign check for Linked Open Vocabularies (LOV) took 0.1790311336517334s
Availability | Check URIs Dereferenciability for Linked Open Vocabularies (LOV) took 5805.907466650009s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.5849752426147461s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.022600173950195312s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 6.103515625e-05s
Interoperability | Check the re-using of existing vocabs for Linked Open Vocabularies (LOV) took 48.79351782798767s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.2874603271484375e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 7614.841264247894s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.25820350646972656s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.020853281021118164s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 4.029273986816406e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 5.7220458984375e-06s
INFO | --- Analysis for linked-periodicals took 2.455897808074951s
Availability | SPARQL endpoint availability check for Linked Index took 4.410743713378906e-05s
Availability | VoID file availability check for Linked Index took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Linked Index took 0.286668062210083s
Reputation | Calculation of the PageRank for Linked Index took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.511543273925781e-05s
Believability | Calculation of trust value for Linked Index took 6.4373016357421875e-06s
INFO | --- Analysis for linked-stockindex took 3.0091664791107178s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 5.239874362945557s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.26686596870422363s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.020882129669189453s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 4.363059997558594e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 9.775161743164062e-06s
INFO | --- Analysis for linked-structured-product-labels took 20.203049659729004s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.32265377044677734s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.29198169708251953s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.021549463272094727s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.000982046127319336s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 4.291534423828125e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 6.67572021484375e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 2.8415379524230957s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.194748163223267s
Availability | VoID file availability check for Linked TCGA took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.2618272304534912s
Reputation | Calculation of the PageRank for Linked TCGA took 0.020710229873657227s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.320808410644531e-05s
Believability | Calculation of trust value for Linked TCGA took 1.0251998901367188e-05s
INFO | --- Analysis for linked-tcga took 62.70521402359009s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.09500288963317871s
Availability | VoID file availability check for Linked User Feedback took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.28223633766174316s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.02303457260131836s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.910064697265625e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.049041748046875e-05s
INFO | --- Analysis for linked-user-feedback took 2.723252534866333s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.482269287109375e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.27486491203308105s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020967960357666016s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.486343383789062e-05s
Believability | Calculation of trust value for USPTO Patent data took 5.0067901611328125e-06s
INFO | --- Analysis for linked-uspto-patent-data took 53.913084983825684s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.06204485893249512s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.2894279956817627s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.020832300186157227s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.314018249511719e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.0251998901367188e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 2.803317070007324s
Availability | SPARQL endpoint availability check for LinkedCT took 2.472308397293091s
Availability | VoID file availability check for LinkedCT took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.27128124237060547s
Reputation | Calculation of the PageRank for LinkedCT took 0.022739887237548828s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.942054748535156e-05s
Believability | Calculation of trust value for LinkedCT took 1.0967254638671875e-05s
INFO | --- Analysis for linkedct took 6.582839727401733s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.14457249641418457s
Availability | VoID file availability check for LinkedGeoData took 0.0004830360412597656s
Extra | Recovery of all triples for LinkedGeoData took 8.196017265319824s
Performance | Total latancy measurement for LinkedGeoData took 0.620539665222168s
Amount of data | Number of triples check for LinkedGeoData took 51.584569692611694s
Interoperability | New terms check for LinkedGeoData took 90.44341564178467s
Versatility | Languages check for LinkedGeoData took 181.9205722808838s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.1816873550415039s
Security | Check HTTPS for LinkedGeoData took 0.3036818504333496s
Interpretability | RDF structures check for LinkedGeoData took 0.14034390449523926s
Versatility | Serialization formats check for LinkedGeoData took 0.14840483665466309s
Availability | RDF dump link check for LinkedGeoData took 0.11843109130859375s
License | MR license check for LinkedGeoData took 0.12083983421325684s
License | HR license check for LinkedGeoData took 90.93124270439148s
Amount of data | Number of property check for LinkedGeoData took 0.1466829776763916s
Understandability | Number of label check for LinkedGeoData took 0.9566371440887451s
Understandability | URI regex check for LinkedGeoData took 0.2717864513397217s
Understandability | Vocabs check for LinkedGeoData took 0.14388132095336914s
Verifiability | Authors check for LinkedGeoData took 0.1336836814880371s
Verifiability | Publishers check for LinkedGeoData took 0.12307906150817871s
Performance | Throughput check for LinkedGeoData took 10.739453792572021s
Amount of data | Check the number of entities for LinkedGeoData took 0.058562278747558594s
Verifiability | Contribs. check for LinkedGeoData took 0.12392210960388184s
Interlinking | sameAs chians check for LinkedGeoData took 0.17541098594665527s
Interlinking | skos check for LinkedGeoData took 0.1410210132598877s
Interlinking | skos check for LinkedGeoData took 0.11245965957641602s
Timeliness | dataset update frequency check for LinkedGeoData took 0.11220049858093262s
Currency | Creation date check for LinkedGeoData took 0.27229952812194824s
Currency | Modification date check for LinkedGeoData took 0.24654936790466309s
Rep.Conc. | URIs length for LinkedGeoData took 272.1937952041626s
Interoperability | New vocabularies check for LinkedGeoData took 1001.6221139431s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.3514227867126465s
Accuracy | Check Functional Property for LinkedGeoData took 0.14289188385009766s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.12711310386657715s
Accuracy | Check Empty annotation labels for LinkedGeoData took 1.5736424922943115s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15598130226135254s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.1347215175628662s
Consistency | Disjoint class check for LinkedGeoData took 0.14240765571594238s
Consistency | Check Misplaced properties for LinkedGeoData took 181.815505027771s
Consistency | Misplaced classes for LinkedGeoData took 0.612795352935791s
Consistency | Check Ontology hijacking for LinkedGeoData took 3.2834279537200928s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.1078822612762451s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 181.4894986152649s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.14433932304382324s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.2653365135192871s
Security | Sign check for LinkedGeoData took 0.1567678451538086s
Availability | Check URIs Dereferenciability for LinkedGeoData took 11.258119344711304s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.48042941093444824s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.02117633819580078s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.0001347064971923828s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 10.860182523727417s
Believability | Calculation of trust value for LinkedGeoData took 1.2874603271484375e-05s
INFO | --- Analysis for linkedgeodata took 3138.5708408355713s
Availability | SPARQL endpoint availability check for LinkedLCCN took 0.9875555038452148s
Availability | VoID file availability check for LinkedLCCN took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.2642333507537842s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.021706342697143555s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010657310485839844s
Believability | Calculation of trust value for LinkedLCCN took 6.628036499023438e-05s
INFO | --- Analysis for linkedlccn took 22.972079277038574s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 8.821487426757812e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.2746143341064453s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.020922183990478516s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.409385681152344e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.0251998901367188e-05s
INFO | --- Analysis for linkedmarkmail took 2.7329938411712646s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.58661103248596s
Availability | VoID file availability check for Linked Movie DataBase took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.26587557792663574s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.020929574966430664s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00013446807861328125s
Believability | Calculation of trust value for Linked Movie DataBase took 1.0967254638671875e-05s
INFO | --- Analysis for linkedmdb took 133.34647345542908s
Availability | SPARQL endpoint availability check for LinkedSpending took 0.41430234909057617s
Availability | VoID file availability check for LinkedSpending took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for LinkedSpending took 0.26249241828918457s
Reputation | Calculation of the PageRank for LinkedSpending took 0.021755218505859375s
Interlinking | Calculation of Degree of Connection for LinkedSpending took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedSpending took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for LinkedSpending took 7.200241088867188e-05s
Believability | Calculation of trust value for LinkedSpending took 1.1920928955078125e-05s
INFO | --- Analysis for linkedspending took 3.9265568256378174s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.1950817108154297s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.2655463218688965s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.021976947784423828s
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.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.0001125335693359375s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.2874603271484375e-05s
INFO | --- Analysis for linklion took 2.619088649749756s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 36.46428728103638s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.29949474334716797s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.021499156951904297s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.173683166503906e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 1.2636184692382812e-05s
INFO | --- Analysis for lista-encabezamientos-materia took 40.66229200363159s
Availability | SPARQL endpoint availability check for lobid-organisations took 0.8571772575378418s
Availability | VoID file availability check for lobid-organisations took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.26262545585632324s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02229475975036621s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 0.00010204315185546875s
Believability | Calculation of trust value for lobid-organisations took 1.1205673217773438e-05s
INFO | --- Analysis for lobid-organisations took 4.969681024551392s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.7280511856079102s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.27287745475769043s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 9.703636169433594e-05s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 1.1444091796875e-05s
INFO | --- Analysis for lobid-resources took 6.779181003570557s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.28557872772216797s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.02361464500427246s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 7.2479248046875e-05s
Believability | Calculation of trust value for Linked Open Colors took 7.3909759521484375e-06s
INFO | --- Analysis for loc took 10.080899715423584s
Availability | SPARQL endpoint availability check for Location Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Location Ontology took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.265164852142334s
Reputation | Calculation of the PageRank for Location Ontology took 0.020825624465942383s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for Location Ontology took 1.1444091796875e-05s
INFO | --- Analysis for Location_Ontology took 3.8737897872924805s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.5299530029296875e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.26963090896606445s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.021142244338989258s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.933906555175781e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 1.1682510375976562e-05s
INFO | --- Analysis for locv took 34.991403579711914s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.6820309162139893s
Availability | VoID file availability check for LOD-a-lot took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.2719109058380127s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.022269248962402344s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.266334533691406e-05s
Believability | Calculation of trust value for LOD-a-lot took 1.1682510375976562e-05s
INFO | --- Analysis for lod-a-lot took 13.890068531036377s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.482269287109375e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.2731742858886719s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.0210878849029541s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.869171142578125e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 9.775161743164062e-06s
INFO | --- Analysis for lod2-project-wiki took 3.0608110427856445s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.564974308013916s
Availability | VoID file availability check for LODAC BDLS took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.2638208866119385s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.02071404457092285s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.033348083496094e-05s
Believability | Calculation of trust value for LODAC BDLS took 1.1444091796875e-05s
INFO | --- Analysis for lodac-bdls took 13.460578203201294s
Availability | SPARQL endpoint availability check for lofd took 0.11986470222473145s
Availability | VoID file availability check for lofd took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for lofd took 0.26099228858947754s
Reputation | Calculation of the PageRank for lofd took 0.021740198135375977s
Interlinking | Calculation of Degree of Connection for lofd took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for lofd took 3.123283386230469e-05s
Believability | Calculation of trust value for lofd took 9.5367431640625e-06s
INFO | --- Analysis for lofd took 2.67474102973938s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 271.07503366470337s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.2926328182220459s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.022667646408081055s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 6.318092346191406e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 8.106231689453125e-06s
INFO | --- Analysis for loius took 585.1147594451904s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.520409107208252s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.2670176029205322s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.0211639404296875s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 6.008148193359375e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 9.298324584960938e-06s
INFO | --- Analysis for london-gazette took 3.7504262924194336s
Availability | SPARQL endpoint availability check for Weather Stations took 8.7738037109375e-05s
Availability | VoID file availability check for Weather Stations took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.28064393997192383s
Reputation | Calculation of the PageRank for Weather Stations took 0.021117210388183594s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.130073547363281e-05s
Believability | Calculation of trust value for Weather Stations took 1.1205673217773438e-05s
INFO | --- Analysis for los_metar took 11.458725929260254s
Availability | SPARQL endpoint availability check for Lotico took 0.8542859554290771s
Availability | VoID file availability check for Lotico took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Lotico took 0.27045178413391113s
Reputation | Calculation of the PageRank for Lotico took 0.022584915161132812s
Interlinking | Calculation of Degree of Connection for Lotico took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.511543273925781e-05s
Believability | Calculation of trust value for Lotico took 1.0728836059570312e-05s
INFO | --- Analysis for lotico took 6.201312065124512s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.3694117069244385s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0007228851318359375s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 1.1111538410186768s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 0.7499184608459473s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.2212657928466797s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.4075522422790527s
Versatility | Languages check for Lower Layer Super Output Areas took 0.9448642730712891s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 30.194002151489258s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.09092354774475098s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.2942543029785156s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.19203639030456543s
Availability | RDF dump link check for Lower Layer Super Output Areas took 46.088701009750366s
License | MR license check for Lower Layer Super Output Areas took 0.6052234172821045s
License | HR license check for Lower Layer Super Output Areas took 30.15153431892395s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.19281291961669922s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.29116129875183105s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.37228846549987793s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.18530797958374023s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.12549924850463867s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.28145503997802734s
Performance | Throughput check for Lower Layer Super Output Areas took 11.421595335006714s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 6.67572021484375e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.1353442668914795s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.3552432060241699s
Interlinking | skos check for Lower Layer Super Output Areas took 0.23750638961791992s
Interlinking | skos check for Lower Layer Super Output Areas took 0.12969040870666504s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.18993926048278809s
Currency | Creation date check for Lower Layer Super Output Areas took 0.3766164779663086s
Currency | Modification date check for Lower Layer Super Output Areas took 0.29164624214172363s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 1.6489498615264893s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.12172794342041016s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.12231850624084473s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.12244462966918945s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.3607513904571533s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 1.0797038078308105s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 0.9995319843292236s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.3730344772338867s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.0001652240753173828s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.3913712501525879s
Security | Sign check for Lower Layer Super Output Areas took 0.12230753898620605s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.28931117057800293s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.021567106246948242s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.075599670410156e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 1.430511474609375e-06s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.0013580322265625e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 268.0807466506958s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.45505475997924805s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0005338191986083984s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 126.0548963546753s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9060027599334717s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.39220404624939s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.042578935623169s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.18827271461487s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.9828548431396484s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.25347352027893066s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.081817865371704s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.275465726852417s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5942325592041016s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2131824493408s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19330787658691406s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.462207078933716s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.8166723251342773s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4103672504425049s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.18261480331420898s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2273564338684082s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.709040880203247s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.390975952148438e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.1822972297668457s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.1827256679534912s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4940807819366455s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4360466003417969s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 5.668251276016235s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.446519136428833s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.23219966888427734s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 146.62803173065186s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.1815025806427002s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.36832690238952637s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3486597537994385s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 43.81432032585144s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.623394250869751s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.5737335681915283s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.18027210235595703s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 86.1531183719635s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.194091796875s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 34.87073802947998s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.2492647171020508s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 87.27905559539795s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6681103706359863s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5439727306365967s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9291081428527832s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.355660915374756s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3530616760253906s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.022037506103515625s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.4809112548828125e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for LPIS_(Poland) took 2305.8168234825134s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.17657184600830078s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0005578994750976562s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 121.23014545440674s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.8855109214782715s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.247187376022339s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 14.034704685211182s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.2192461490631s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.894843339920044s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.26442694664001465s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.836620807647705s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.28342580795288086s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5871596336364746s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.1709055900574s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18007349967956543s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.9819154739379883s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.8723869323730469s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.43654966354370117s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18574070930480957s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.24154996871948242s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 10.668746709823608s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 6.747245788574219e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.17597746849060059s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1792752742767334s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.41520190238952637s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4220762252807617s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 6.01564621925354s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.43262386322021484s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.23224925994873047s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 154.46682143211365s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18282198905944824s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1705026626586914s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3174593448638916s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 40.06533932685852s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.6266610622406006s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.647796154022217s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.17824578285217285s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 85.73705649375916s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.099857568740845s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 34.007328033447266s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.2108097076416016s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 87.36872553825378s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7406702041625977s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5154178142547607s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.865971565246582s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 12.978670835494995s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5191125869750977s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.026564598083496094s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.3855438232421875e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1444091796875e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 2274.4753589630127s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 5.0067901611328125e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.2759420871734619s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.022925615310668945s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.001142263412475586s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 4.1961669921875e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 1.1205673217773438e-05s
INFO | --- Analysis for lremap-auth took 3.146204948425293s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 8.559226989746094e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.2702956199645996s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.020457744598388672s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 2.8848648071289062e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.1205673217773438e-05s
INFO | --- Analysis for lremap-conf took 2.7776646614074707s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 9.131431579589844e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.29825496673583984s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020872831344604492s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.266334533691406e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.2159347534179688e-05s
INFO | --- Analysis for lremap-ri took 2.7490007877349854s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 8.96453857421875e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.2678642272949219s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.021131277084350586s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.3855438232421875e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.1682510375976562e-05s
INFO | --- Analysis for lremap-sub took 2.788403034210205s
Availability | SPARQL endpoint availability check for LSQ took 4.267692565917969e-05s
Availability | VoID file availability check for LSQ took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for LSQ took 0.263272762298584s
Reputation | Calculation of the PageRank for LSQ took 0.020974397659301758s
Interlinking | Calculation of Degree of Connection for LSQ took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.4332275390625e-05s
Believability | Calculation of trust value for LSQ took 1.1920928955078125e-05s
INFO | --- Analysis for lsq took 3.530139446258545s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.5220012664794922s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0003826618194580078s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.2829620838165283s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.021626710891723633s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 4.863739013671875e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for LucaniPharsalia took 3.9851675033569336s
Availability | SPARQL endpoint availability check for Linked rules took 4.3392181396484375e-05s
Availability | VoID file availability check for Linked rules took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Linked rules took 0.2728264331817627s
Reputation | Calculation of the PageRank for Linked rules took 0.021033048629760742s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0008344650268554688s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.457069396972656e-05s
Believability | Calculation of trust value for Linked rules took 7.152557373046875e-06s
INFO | --- Analysis for Luminaires_senlis took 2.3853375911712646s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.184401988983154s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.29638099670410156s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.023282527923583984s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 3.409385681152344e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 1.239776611328125e-05s
INFO | --- Analysis for makg took 63.432345390319824s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 8.678436279296875e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.27224254608154297s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.0214388370513916s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.719329833984375e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 1.1444091796875e-05s
INFO | --- Analysis for manchester-university-reading-lists took 3.255812168121338s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 8.893013000488281e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.002288818359375s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.269366979598999s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020992517471313477s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.7670135498046875e-05s
Believability | Calculation of trust value for engineering equipment ontology took 9.775161743164062e-06s
INFO | --- Analysis for manish took 2.520822286605835s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.124641418457031e-05s
Availability | VoID file availability check for MARC Codes List took 0.00031638145446777344s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.27309751510620117s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020679712295532227s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.0001277923583984375s
Believability | Calculation of trust value for MARC Codes List took 1.049041748046875e-05s
INFO | --- Analysis for marc-codes took 18.830819606781006s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 8.368492126464844e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.26633119583129883s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.02100682258605957s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.1484832763671875e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.0013580322265625e-05s
INFO | --- Analysis for masc took 10.82456636428833s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 8.535385131835938e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.3004934787750244s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.021087646484375s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 4.0531158447265625e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.0728836059570312e-05s
INFO | --- Analysis for masc-bn-nif took 2.5155727863311768s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.103452444076538s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0002129077911376953s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.2528109550476074s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.02089214324951172s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.0994415283203125e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 6.198883056640625e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 3.570603132247925s
Availability | SPARQL endpoint availability check for medline took 7.43865966796875e-05s
Availability | VoID file availability check for medline took 0.00030303001403808594s
Completeness | Calculation of interlinking completeness for medline took 0.29305577278137207s
Reputation | Calculation of the PageRank for medline took 0.021147489547729492s
Interlinking | Calculation of Degree of Connection for medline took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for medline took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for medline took 4.9114227294921875e-05s
Believability | Calculation of trust value for medline took 5.4836273193359375e-06s
INFO | --- Analysis for medline took 12.124806642532349s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.3950409889221191s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.00042057037353515625s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.29085421562194824s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.02077341079711914s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.771087646484375e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 5.7220458984375e-06s
INFO | --- Analysis for meducator took 12.813570022583008s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.220008850097656e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.00020933151245117188s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.25462841987609863s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.020681142807006836s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 6.961822509765625e-05s
Believability | Calculation of trust value for MetaShare metadata model took 6.4373016357421875e-06s
INFO | --- Analysis for metashare took 2.467613935470581s
Availability | SPARQL endpoint availability check for MExiCo took 7.224082946777344e-05s
Availability | VoID file availability check for MExiCo took 0.00035071372985839844s
Completeness | Calculation of interlinking completeness for MExiCo took 0.25487756729125977s
Reputation | Calculation of the PageRank for MExiCo took 0.02075052261352539s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.8160552978515625e-05s
Believability | Calculation of trust value for MExiCo took 5.4836273193359375e-06s
INFO | --- Analysis for mexico took 22.61530566215515s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 0.999873161315918s
Availability | VoID file availability check for Coronavirus dataset took 0.000217437744140625s
Extra | Recovery of all triples for Coronavirus dataset took 5.718960523605347s
Performance | Total latancy measurement for Coronavirus dataset took 2.4190926551818848s
Amount of data | Number of triples check for Coronavirus dataset took 1.2248280048370361s
Interoperability | New terms check for Coronavirus dataset took 2.3776962757110596s
Versatility | Languages check for Coronavirus dataset took 60.50044798851013s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.446098566055298s
Interpretability | RDF structures check for Coronavirus dataset took 0.5217380523681641s
Versatility | Serialization formats check for Coronavirus dataset took 0.5298900604248047s
Availability | RDF dump link check for Coronavirus dataset took 0.48526930809020996s
License | MR license check for Coronavirus dataset took 0.5380089282989502s
License | HR license check for Coronavirus dataset took 42.2540180683136s
Amount of data | Number of property check for Coronavirus dataset took 0.526308536529541s
Understandability | Number of label check for Coronavirus dataset took 1.4888525009155273s
Understandability | URI regex check for Coronavirus dataset took 0.9712769985198975s
Understandability | Vocabs check for Coronavirus dataset took 0.48656558990478516s
Verifiability | Authors check for Coronavirus dataset took 0.5435507297515869s
Verifiability | Publishers check for Coronavirus dataset took 0.48686647415161133s
Performance | Throughput check for Coronavirus dataset took 14.396888256072998s
Amount of data | Check the number of entities for Coronavirus dataset took 6.842613220214844e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.48747897148132324s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5096147060394287s
Interlinking | skos check for Coronavirus dataset took 0.5279171466827393s
Interlinking | skos check for Coronavirus dataset took 0.4823784828186035s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.49460864067077637s
Currency | Creation date check for Coronavirus dataset took 0.9969143867492676s
Currency | Modification date check for Coronavirus dataset took 0.992762565612793s
Rep.Conc. | URIs length for Coronavirus dataset took 8.405705690383911s
Interoperability | New vocabularies check for Coronavirus dataset took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.505303144454956s
Accuracy | Check Functional Property for Coronavirus dataset took 0.7544376850128174s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.7359249591827393s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.104207754135132s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.022323131561279297s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.02785944938659668s
Consistency | Disjoint class check for Coronavirus dataset took 1.0362567901611328s
Consistency | Check Misplaced properties for Coronavirus dataset took 7.5823376178741455s
Consistency | Misplaced classes for Coronavirus dataset took 0.6005356311798096s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.179577589035034s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.1136970520019531s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.559855222702026s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.032430410385131836s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5159497261047363s
Security | Sign check for Coronavirus dataset took 0.510291337966919s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 2995.2923357486725s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.6799242496490479s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021190404891967773s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 6.008148193359375e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Coronavirus dataset took 9.775161743164062e-06s
INFO | --- Analysis for micro-coronavirus took 3230.434147119522s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 4.673004150390625e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.2859196662902832s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.02172565460205078s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00011086463928222656s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.4066696166992188e-05s
INFO | --- Analysis for miguiadeviajes-gnoss took 5.96560525894165s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0001087188720703125s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.2642078399658203s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020863771438598633s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00010633468627929688s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for mismuseos-gnoss took 8.703186273574829s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.08310198783874512s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.2609837055206299s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020922422409057617s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.363059997558594e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.3113021850585938e-05s
INFO | --- Analysis for mlsa took 3.0201613903045654s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 0.00012063980102539062s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.2799520492553711s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.361701965332031e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 9.775161743164062e-06s
INFO | --- Analysis for model took 31.809221267700195s
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 0.00010442733764648438s
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.0007474422454833984s
Completeness | Calculation of interlinking completeness for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.30601954460144043s
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.020975112915039062s
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.0967254638671875e-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.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 3.170967102050781e-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.0013580322265625e-05s
INFO | --- Analysis for model1 took 21.18193292617798s
Availability | SPARQL endpoint availability check for MORElab took 0.855870246887207s
Availability | VoID file availability check for MORElab took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for MORElab took 0.2664041519165039s
Reputation | Calculation of the PageRank for MORElab took 0.02282238006591797s
Interlinking | Calculation of Degree of Connection for MORElab took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.440017700195312e-05s
Believability | Calculation of trust value for MORElab took 1.0013580322265625e-05s
INFO | --- Analysis for morelab took 5.898276329040527s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 1.7306222915649414s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0008111000061035156s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.26401734352111816s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.02190423011779785s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.606910705566406e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 1.0013580322265625e-05s
INFO | --- Analysis for msc took 16.121289014816284s
Availability | SPARQL endpoint availability check for Multext-East took 4.124641418457031e-05s
Availability | VoID file availability check for Multext-East took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for Multext-East took 0.26233887672424316s
Reputation | Calculation of the PageRank for Multext-East took 0.02086329460144043s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.62396240234375e-05s
Believability | Calculation of trust value for Multext-East took 7.152557373046875e-06s
INFO | --- Analysis for multext-east took 2.464970588684082s
Availability | SPARQL endpoint availability check for Multimedia Lab took 9.679794311523438e-05s
Availability | VoID file availability check for Multimedia Lab took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.2637200355529785s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.647804260253906e-05s
Believability | Calculation of trust value for Multimedia Lab took 1.0251998901367188e-05s
INFO | --- Analysis for multimedia-lab took 2.4645793437957764s
Availability | SPARQL endpoint availability check for Muninn World War I took 3.246112108230591s
Availability | VoID file availability check for Muninn World War I took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.26762866973876953s
Reputation | Calculation of the PageRank for Muninn World War I took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.058547973632812e-05s
Believability | Calculation of trust value for Muninn World War I took 1.1444091796875e-05s
INFO | --- Analysis for muninn-world-war-i took 16.455979347229004s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 5.340576171875e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.2873039245605469s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.020786046981811523s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00010824203491210938s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.0967254638671875e-05s
INFO | --- Analysis for museosespania-gnoss took 95.46128439903259s
Availability | SPARQL endpoint availability check for Italian Museums took 0.34008145332336426s
Availability | VoID file availability check for Italian Museums took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.26952457427978516s
Reputation | Calculation of the PageRank for Italian Museums took 0.02097916603088379s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.177757263183594e-05s
Believability | Calculation of trust value for Italian Museums took 1.0251998901367188e-05s
INFO | --- Analysis for museums-in-italy took 2.8368420600891113s
Availability | SPARQL endpoint availability check for Muziekweb took 2.4344019889831543s
Availability | VoID file availability check for Muziekweb took 0.0006415843963623047s
Extra | Recovery of all triples for Muziekweb took 3.338134288787842s
Performance | Total latancy measurement for Muziekweb took 7.921112775802612s
Amount of data | Number of triples check for Muziekweb took 1.5851237773895264s
Interoperability | New terms check for Muziekweb took 2.6300182342529297s
Versatility | Languages check for Muziekweb took 51.80885410308838s
Interpretability | Number of blank nodes check for Muziekweb took 1.2662992477416992s
Interpretability | RDF structures check for Muziekweb took 1.4339807033538818s
Versatility | Serialization formats check for Muziekweb took 1.2137229442596436s
Availability | RDF dump link check for Muziekweb took 1.1617484092712402s
License | MR license check for Muziekweb took 1.3727610111236572s
License | HR license check for Muziekweb took 12.712432384490967s
Amount of data | Number of property check for Muziekweb took 1.5783154964447021s
Understandability | Number of label check for Muziekweb took 1.4201152324676514s
Understandability | URI regex check for Muziekweb took 4.344298839569092s
Understandability | Vocabs check for Muziekweb took 2.607278823852539s
Verifiability | Authors check for Muziekweb took 1.4273808002471924s
Verifiability | Publishers check for Muziekweb took 2.5657527446746826s
Performance | Throughput check for Muziekweb took 18.7465500831604s
Amount of data | Check the number of entities for Muziekweb took 7.176399230957031e-05s
Verifiability | Contribs. check for Muziekweb took 1.4132652282714844s
Interlinking | sameAs chians check for Muziekweb took 1.6609995365142822s
Interlinking | skos check for Muziekweb took 2.387949228286743s
Interlinking | skos check for Muziekweb took 1.1694004535675049s
Timeliness | dataset update frequency check for Muziekweb took 1.3814961910247803s
Currency | Creation date check for Muziekweb took 3.3346831798553467s
Currency | Modification date check for Muziekweb took 2.776475429534912s
Rep.Conc. | URIs length for Muziekweb took 7.281423091888428s
Interoperability | New vocabularies check for Muziekweb took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 1.541452407836914s
Accuracy | Check Empty annotation labels for Muziekweb took 5.837308168411255s
Accuracy | Check White space in annotation for Muziekweb took 0.02746129035949707s
Accuracy | Check Datatype consistency for Muziekweb took 0.028908729553222656s
Consistency | Disjoint class check for Muziekweb took 2.669067621231079s
Consistency | Check Misplaced properties for Muziekweb took 3.434217929840088s
Consistency | Check Ontology hijacking for Muziekweb took 2.9504947662353516s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.1194541454315186s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 2.7636234760284424s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03239750862121582s
Conciseness | Check Intensional conciseness for Muziekweb took 2.61635160446167s
Security | Sign check for Muziekweb took 1.5294480323791504s
Availability | Check URIs Dereferenciability for Muziekweb took 5721.909850358963s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.7661283016204834s
Reputation | Calculation of the PageRank for Muziekweb took 0.021609067916870117s
Interlinking | Calculation of Degree of Connection for Muziekweb took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0009129047393798828s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 7.176399230957031e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.9073486328125e-06s
Believability | Calculation of trust value for Muziekweb took 1.1920928955078125e-05s
INFO | --- Analysis for muziekweb took 5939.30192732811s
Availability | SPARQL endpoint availability check for myExperiment took 0.6206152439117432s
Availability | VoID file availability check for myExperiment took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for myExperiment took 0.2909872531890869s
Reputation | Calculation of the PageRank for myExperiment took 0.022064208984375s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for myExperiment took 9.942054748535156e-05s
Believability | Calculation of trust value for myExperiment took 1.239776611328125e-05s
INFO | --- Analysis for my-experiment took 4.371264457702637s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.062169790267944336s
Availability | VoID file availability check for My Family Lineage took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.27065086364746094s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020895957946777344s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.440017700195312e-05s
Believability | Calculation of trust value for My Family Lineage took 9.298324584960938e-06s
INFO | --- Analysis for my-family-lineage took 3.7249152660369873s
Availability | SPARQL endpoint availability check for My ontology test took 1.1430943012237549s
Availability | VoID file availability check for My ontology test took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for My ontology test took 0.27248239517211914s
Reputation | Calculation of the PageRank for My ontology test took 0.02116680145263672s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.0279159545898438e-05s
Believability | Calculation of trust value for My ontology test took 1.2159347534179688e-05s
INFO | --- Analysis for myontologytest took 3.7611851692199707s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 8.726119995117188e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.27225184440612793s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020850419998168945s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 9.918212890625e-05s
Believability | Calculation of trust value for myopenlink dataspaces took 1.0251998901367188e-05s
INFO | --- Analysis for myopenlink-dataspaces took 3.965292453765869s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 6.136063098907471s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.28805088996887207s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.021080970764160156s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.699562072753906e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 7.62939453125e-06s
INFO | --- Analysis for n-lex-as-linked-data took 15.74406361579895s
Availability | SPARQL endpoint availability check for NAICS 2007 took 83.53622770309448s
Availability | VoID file availability check for NAICS 2007 took 0.0006773471832275391s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.3506636619567871s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.020989418029785156s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 3.7670135498046875e-05s
Believability | Calculation of trust value for NAICS 2007 took 8.821487426757812e-06s
INFO | --- Analysis for naics-2007 took 384.1931850910187s
Availability | SPARQL endpoint availability check for NAICS 2012 took 42.40872764587402s
Availability | VoID file availability check for NAICS 2012 took 0.0008714199066162109s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.30808138847351074s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.021113157272338867s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.793571472167969e-05s
Believability | Calculation of trust value for NAICS 2012 took 8.344650268554688e-06s
INFO | --- Analysis for naics-2012 took 268.56191301345825s
Availability | SPARQL endpoint availability check for Usernames  took 9.036064147949219e-05s
Availability | VoID file availability check for Usernames  took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Usernames  took 0.26979613304138184s
Reputation | Calculation of the PageRank for Usernames  took 0.021132946014404297s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.123283386230469e-05s
Believability | Calculation of trust value for Usernames  took 1.049041748046875e-05s
INFO | --- Analysis for Names took 2.4409823417663574s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.2308738231658936s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0006442070007324219s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.3394653797149658s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 2.5231192111968994s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 13.517353773117065s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 16.68316674232483s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.7586970329284668s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.914396524429321s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.747572660446167s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.7742166519165039s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.3297140598297119s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.32071948051452637s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.3177931308746338s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.75951981544495s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.400709867477417s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 6.8291380405426025s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.644603967666626s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.7765483856201172s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.32707715034484863s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.3255181312561035s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 14.398725271224976s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 8.821487426757812e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.7734780311584473s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.8869795799255371s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.8148741722106934s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.02492094039917s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.3269631862640381s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.0052385330200195s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 1.1114935874938965s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 0.6803033351898193s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.32062268257141113s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.7602152824401855s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3238675594329834s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.34559035301208496s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007398128509521484s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0005450248718261719s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.32048773765563965s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.6582131385803223s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.3229091167449951s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.5085675716400146s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.1591293811798096s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.4995427131652832s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0006639957427978516s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.3656742572784424s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 4.981339454650879s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.3016085624694824s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.021002769470214844s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.198883056640625e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.1920928955078125e-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 237.00431370735168s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.7740077972412109s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0005197525024414062s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.3193745613098145s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 2.4929392337799072s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.365573644638062s
Interoperability | New terms check for National Diet Library of Japan subject headings took 14.744763612747192s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.7801969051361084s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.482665777206421s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.7715551853179932s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.3290266990661621s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.3245515823364258s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.31487417221069336s
License | MR license check for National Diet Library of Japan subject headings took 0.7755072116851807s
License | HR license check for National Diet Library of Japan subject headings took 91.27754187583923s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8356218338012695s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.204458475112915s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.644451379776001s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.7689218521118164s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.32762670516967773s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.33774757385253906s
Performance | Throughput check for National Diet Library of Japan subject headings took 12.541566371917725s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.7738037109375e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.32834291458129883s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.4258594512939453s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.3256559371948242s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.2424964904785156s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.32808566093444824s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.4207572937011719s
Currency | Modification date check for National Diet Library of Japan subject headings took 1.0953340530395508s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.6474275588989258s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.32763171195983887s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.321408748626709s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.3218190670013428s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.3422660827636719s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007529258728027344s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0010313987731933594s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.32050275802612305s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 1.0804808139801025s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.3283836841583252s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.4725227355957031s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.1197550296783447s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.4347031116485596s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0007002353668212891s
Security | Sign check for National Diet Library of Japan subject headings took 0.7913358211517334s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 4.992610692977905s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.35421252250671387s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02093791961669922s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.52587890625e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.364418029785156e-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.0251998901367188e-05s
INFO | --- Analysis for national-diet-library-subject-headings took 228.97780084609985s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.1160905361175537s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.26765942573547363s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.02207779884338379s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.839897155761719e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 1.0728836059570312e-05s
INFO | --- Analysis for national-library-of-greece-authority-records took 5.2615437507629395s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.749961853027344e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2754812240600586s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02296304702758789s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.081031799316406e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.1444091796875e-05s
INFO | --- Analysis for Naturopathy took 3.4276068210601807s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.9504244327545166s
Availability | VoID file availability check for COVID-19 Data took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.2749521732330322s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.021312236785888672s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0009410381317138672s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.409385681152344e-05s
Believability | Calculation of trust value for COVID-19 Data took 1.0967254638671875e-05s
INFO | --- Analysis for NCMI-COVID-19 took 7.839294672012329s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.3789596557617188s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.26744675636291504s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.021780014038085938s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.1920928955078125e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 1.1205673217773438e-05s
INFO | --- Analysis for NCMICOVID-19 took 6.243543386459351s
Availability | SPARQL endpoint availability check for Near took 4.2438507080078125e-05s
Availability | VoID file availability check for Near took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for Near took 0.27713871002197266s
Reputation | Calculation of the PageRank for Near took 0.02299022674560547s
Interlinking | Calculation of Degree of Connection for Near took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Near took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Near took 8.893013000488281e-05s
Believability | Calculation of trust value for Near took 1.1682510375976562e-05s
INFO | --- Analysis for near took 12.447264194488525s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 5.602836608886719e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.2689340114593506s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.0207216739654541s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 2.9087066650390625e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.239776611328125e-05s
INFO | --- Analysis for neurolex-wiki took 2.4109668731689453s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 0.000102996826171875s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.2751150131225586s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.02129840850830078s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.3392181396484375e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 1.1682510375976562e-05s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 4.450820207595825s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 9.584426879882812e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.2761709690093994s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.866455078125e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 1.1205673217773438e-05s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.631662607192993s
Availability | SPARQL endpoint availability check for neXtProt took 2.01357102394104s
Availability | VoID file availability check for neXtProt took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for neXtProt took 0.2634248733520508s
Reputation | Calculation of the PageRank for neXtProt took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.4809112548828125e-05s
Believability | Calculation of trust value for neXtProt took 9.5367431640625e-06s
INFO | --- Analysis for nextprot took 5.07862114906311s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 9.608268737792969e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.2682685852050781s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.020670175552368164s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010323524475097656s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.0967254638671875e-05s
INFO | --- Analysis for nextweb-gnoss took 9.160934925079346s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 8.749961853027344e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.26920127868652344s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.020998477935791016s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.0108642578125e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 8.58306884765625e-06s
INFO | --- Analysis for nhs-jargon took 2.9500958919525146s
Availability | SPARQL endpoint availability check for NIT Patna took 8.749961853027344e-05s
Availability | VoID file availability check for NIT Patna took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.2622182369232178s
Reputation | Calculation of the PageRank for NIT Patna took 0.021490812301635742s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.866455078125e-05s
Believability | Calculation of trust value for NIT Patna took 1.2159347534179688e-05s
INFO | --- Analysis for NITP took 3.289886236190796s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 5.5789947509765625e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.2640094757080078s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.022278547286987305s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for nlr-dataset-mod took 3.782973289489746s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.5240700244903564s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.2613828182220459s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.022153377532958984s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 9.298324584960938e-06s
INFO | --- Analysis for NLW took 3.968031167984009s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.396662712097168s
Availability | VoID file availability check for Nobel Prizes took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.266848087310791s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.020717382431030273s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.417533874511719e-05s
Believability | Calculation of trust value for Nobel Prizes took 6.9141387939453125e-06s
INFO | --- Analysis for nobelprizes took 9.320111751556396s
Availability | SPARQL endpoint availability check for NoiPA took 0.31823277473449707s
Availability | VoID file availability check for NoiPA took 0.0003256797790527344s
Extra | Recovery of all triples for NoiPA took 1.9414632320404053s
Performance | Total latancy measurement for NoiPA took 0.7361738681793213s
Amount of data | Number of triples check for NoiPA took 9.061389446258545s
Interoperability | New terms check for NoiPA took 2.7452120780944824s
Versatility | Languages check for NoiPA took 60.2038459777832s
Interpretability | Number of blank nodes check for NoiPA took 0.29964494705200195s
Interpretability | RDF structures check for NoiPA took 0.6484622955322266s
Versatility | Serialization formats check for NoiPA took 0.4062490463256836s
Availability | RDF dump link check for NoiPA took 0.2941148281097412s
License | MR license check for NoiPA took 0.9438471794128418s
License | HR license check for NoiPA took 60.19425344467163s
Amount of data | Number of property check for NoiPA took 0.24711251258850098s
Understandability | Number of label check for NoiPA took 1.4702262878417969s
Understandability | URI regex check for NoiPA took 0.625922679901123s
Understandability | Vocabs check for NoiPA took 0.19210147857666016s
Verifiability | Authors check for NoiPA took 0.27520155906677246s
Verifiability | Publishers check for NoiPA took 0.252835750579834s
Performance | Throughput check for NoiPA took 10.475769758224487s
Amount of data | Check the number of entities for NoiPA took 7.605552673339844e-05s
Verifiability | Contribs. check for NoiPA took 0.226670503616333s
Interlinking | sameAs chians check for NoiPA took 0.6824038028717041s
Interlinking | skos check for NoiPA took 0.7442378997802734s
Interlinking | skos check for NoiPA took 0.14279437065124512s
Timeliness | dataset update frequency check for NoiPA took 0.2692263126373291s
Currency | Creation date check for NoiPA took 0.48227977752685547s
Currency | Modification date check for NoiPA took 0.21181225776672363s
Rep.Conc. | URIs length for NoiPA took 19.522910833358765s
Interoperability | New vocabularies check for NoiPA took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.1911602020263672s
Accuracy | Check Functional Property for NoiPA took 0.19187068939208984s
Accuracy | Check Inverse Functional Property for NoiPA took 0.1610870361328125s
Accuracy | Check Empty annotation labels for NoiPA took 0.5775785446166992s
Accuracy | Check White space in annotation for NoiPA took 0.02568674087524414s
Accuracy | Check Datatype consistency for NoiPA took 0.03312945365905762s
Consistency | Disjoint class check for NoiPA took 0.15419983863830566s
Consistency | Check Misplaced properties for NoiPA took 17.072367906570435s
Consistency | Misplaced classes for NoiPA took 0.2069249153137207s
Consistency | Check Ontology hijacking for NoiPA took 1.7948355674743652s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.149367094039917s
Consistency | Check Invalid usage of undefined properties for NoiPA took 18.295929670333862s
Conciseness | Check Extensional conciseness for NoiPA took 0.0344693660736084s
Conciseness | Check Intensional conciseness for NoiPA took 0.16885614395141602s
Security | Sign check for NoiPA took 0.12252521514892578s
Availability | Check URIs Dereferenciability for NoiPA took 20.27669620513916s
Completeness | Calculation of interlinking completeness for NoiPA took 0.41099023818969727s
Reputation | Calculation of the PageRank for NoiPA took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for NoiPA took 4.029273986816406e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.1920928955078125e-06s
Believability | Calculation of trust value for NoiPA took 5.7220458984375e-06s
INFO | --- Analysis for NoiPA took 587.276209115982s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 1.1606264114379883s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.29819154739379883s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.020734786987304688s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.131431579589844e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.2159347534179688e-05s
INFO | --- Analysis for nom took 7.885791301727295s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 28.18869638442993s
Availability | VoID file availability check for Nomenclator Asturias took 0.0008075237274169922s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.2657647132873535s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.153915405273438e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 8.344650268554688e-06s
INFO | --- Analysis for nomenclator-asturias took 142.45003581047058s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.3731052875518799s
Availability | VoID file availability check for Nomisma.org  took 0.0003814697265625s
Extra | Recovery of all triples for Nomisma.org  took 493.03467774391174s
Performance | Total latancy measurement for Nomisma.org  took 2.5157949924468994s
Amount of data | Number of triples check for Nomisma.org  took 34.32094430923462s
Interoperability | New terms check for Nomisma.org  took 6.192938327789307s
Versatility | Languages check for Nomisma.org  took 114.44498062133789s
Interpretability | Number of blank nodes check for Nomisma.org  took 56.509244441986084s
Security | Check HTTPS for Nomisma.org  took 0.7097001075744629s
Interpretability | RDF structures check for Nomisma.org  took 1.4121558666229248s
Versatility | Serialization formats check for Nomisma.org  took 0.3186967372894287s
Availability | RDF dump link check for Nomisma.org  took 1193.901742696762s
License | MR license check for Nomisma.org  took 0.34276700019836426s
License | HR license check for Nomisma.org  took 66.21893811225891s
Amount of data | Number of property check for Nomisma.org  took 0.3621835708618164s
Understandability | Number of label check for Nomisma.org  took 9.596181631088257s
Understandability | URI regex check for Nomisma.org  took 0.7516465187072754s
Understandability | Vocabs check for Nomisma.org  took 0.2969093322753906s
Verifiability | Authors check for Nomisma.org  took 0.2937324047088623s
Verifiability | Publishers check for Nomisma.org  took 0.32132816314697266s
Performance | Throughput check for Nomisma.org  took 12.40187931060791s
Amount of data | Check the number of entities for Nomisma.org  took 0.0008435249328613281s
Verifiability | Contribs. check for Nomisma.org  took 0.3312091827392578s
Interlinking | sameAs chians check for Nomisma.org  took 0.3119032382965088s
Interlinking | skos check for Nomisma.org  took 1.195255994796753s
Interlinking | skos check for Nomisma.org  took 0.4622466564178467s
Timeliness | dataset update frequency check for Nomisma.org  took 0.293529748916626s
Currency | Creation date check for Nomisma.org  took 0.6123685836791992s
Currency | Modification date check for Nomisma.org  took 0.6086220741271973s
Rep.Conc. | URIs length for Nomisma.org  took 375.73265624046326s
Interoperability | New vocabularies check for Nomisma.org  took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.3156893253326416s
Accuracy | Check Functional Property for Nomisma.org  took 0.31447577476501465s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.29225897789001465s
Accuracy | Check Empty annotation labels for Nomisma.org  took 116.27290058135986s
Accuracy | Check White space in annotation for Nomisma.org  took 2.72161602973938s
Consistency | Disjoint class check for Nomisma.org  took 0.31468820571899414s
Consistency | Check Misplaced properties for Nomisma.org  took 29.73034977912903s
Consistency | Check Ontology hijacking for Nomisma.org  took 93.57035517692566s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 27.36347532272339s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.00016117095947265625s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.33120274543762207s
Security | Sign check for Nomisma.org  took 0.2925701141357422s
Availability | Check URIs Dereferenciability for Nomisma.org  took 1614.969405412674s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 5.626953601837158s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.021696805953979492s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 5.173683166503906e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.430511474609375e-06s
Believability | Calculation of trust value for Nomisma.org  took 6.9141387939453125e-06s
INFO | --- Analysis for nomisma_org took 8028.313759326935s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.32696056365966797s
Availability | VoID file availability check for Curriculum Vitae took 0.0004999637603759766s
Extra | Recovery of all triples for Curriculum Vitae took 0.5463716983795166s
Performance | Total latancy measurement for Curriculum Vitae took 0.9637546539306641s
Amount of data | Number of triples check for Curriculum Vitae took 0.1221456527709961s
Interoperability | New terms check for Curriculum Vitae took 1.2390241622924805s
Versatility | Languages check for Curriculum Vitae took 0.11890697479248047s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.10856127738952637s
Interpretability | RDF structures check for Curriculum Vitae took 0.21137261390686035s
Versatility | Serialization formats check for Curriculum Vitae took 0.12618660926818848s
Availability | RDF dump link check for Curriculum Vitae took 0.1176900863647461s
License | MR license check for Curriculum Vitae took 0.10992789268493652s
License | HR license check for Curriculum Vitae took 0.12249469757080078s
Amount of data | Number of property check for Curriculum Vitae took 0.11263060569763184s
Understandability | Number of label check for Curriculum Vitae took 0.12247157096862793s
Understandability | URI regex check for Curriculum Vitae took 0.3468186855316162s
Understandability | Vocabs check for Curriculum Vitae took 0.10896801948547363s
Verifiability | Authors check for Curriculum Vitae took 0.109130859375s
Verifiability | Publishers check for Curriculum Vitae took 0.11972999572753906s
Performance | Throughput check for Curriculum Vitae took 10.763980865478516s
Amount of data | Check the number of entities for Curriculum Vitae took 0.00011038780212402344s
Verifiability | Contribs. check for Curriculum Vitae took 0.13743090629577637s
Interlinking | sameAs chians check for Curriculum Vitae took 0.11363863945007324s
Interlinking | skos check for Curriculum Vitae took 0.4191250801086426s
Interlinking | skos check for Curriculum Vitae took 0.1152188777923584s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.11471867561340332s
Currency | Creation date check for Curriculum Vitae took 0.23383116722106934s
Currency | Modification date check for Curriculum Vitae took 0.2260432243347168s
Rep.Conc. | URIs length for Curriculum Vitae took 0.3023393154144287s
Interoperability | New vocabularies check for Curriculum Vitae took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.12676143646240234s
Accuracy | Check Functional Property for Curriculum Vitae took 0.12245416641235352s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.10883307456970215s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.11234903335571289s
Accuracy | Check White space in annotation for Curriculum Vitae took 0.00011396408081054688s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.003490924835205078s
Consistency | Disjoint class check for Curriculum Vitae took 0.1168355941772461s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.23100709915161133s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.2308707237243652s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.1114070415496826s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.2236883640289307s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.001371145248413086s
Security | Sign check for Curriculum Vitae took 0.1352090835571289s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 18.64275097846985s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.26412081718444824s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 3.1948089599609375e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.6689300537109375e-06s
Believability | Calculation of trust value for Curriculum Vitae took 1.0013580322265625e-05s
INFO | --- Analysis for Nordine_Bittich took 54.16816258430481s
Availability | SPARQL endpoint availability check for NorPark took 0.1606886386871338s
Availability | VoID file availability check for NorPark took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for NorPark took 0.27817440032958984s
Reputation | Calculation of the PageRank for NorPark took 0.02221989631652832s
Interlinking | Calculation of Degree of Connection for NorPark took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.267692565917969e-05s
Believability | Calculation of trust value for NorPark took 1.1682510375976562e-05s
INFO | --- Analysis for norpark took 2.721834897994995s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.015996694564819336s
Availability | VoID file availability check for Parking Dataset took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.2641170024871826s
Reputation | Calculation of the PageRank for Parking Dataset took 0.02206563949584961s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.315376281738281e-05s
Believability | Calculation of trust value for Parking Dataset took 9.298324584960938e-06s
INFO | --- Analysis for norpark2 took 2.4553306102752686s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.5328176021575928s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.00046896934509277344s
Extra | Recovery of all triples for Norway fishery stocks dataset took 121.71134972572327s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.8761928081512451s
Amount of data | Number of triples check for Norway fishery stocks dataset took 9.545085430145264s
Interoperability | New terms check for Norway fishery stocks dataset took 13.827133655548096s
Versatility | Languages check for Norway fishery stocks dataset took 300.23005843162537s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 2.0276429653167725s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.21278762817382812s
Versatility | Serialization formats check for Norway fishery stocks dataset took 8.524936437606812s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.271181583404541s
License | MR license check for Norway fishery stocks dataset took 0.6515097618103027s
License | HR license check for Norway fishery stocks dataset took 300.22075867652893s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.183762788772583s
Understandability | Number of label check for Norway fishery stocks dataset took 1.8151037693023682s
Understandability | URI regex check for Norway fishery stocks dataset took 0.621084451675415s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.3451831340789795s
Verifiability | Authors check for Norway fishery stocks dataset took 0.1810755729675293s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.2306365966796875s
Performance | Throughput check for Norway fishery stocks dataset took 10.649498224258423s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 4.267692565917969e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.17777323722839355s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.18082642555236816s
Interlinking | skos check for Norway fishery stocks dataset took 0.45999956130981445s
Interlinking | skos check for Norway fishery stocks dataset took 0.39292144775390625s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 4.139161825180054s
Currency | Creation date check for Norway fishery stocks dataset took 0.42637062072753906s
Currency | Modification date check for Norway fishery stocks dataset took 0.2253589630126953s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 154.9021065235138s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.17747044563293457s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.25078606605529785s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.2479703426361084s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 33.90494728088379s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.630577564239502s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.5485310554504395s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.17746233940124512s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 87.77667832374573s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.107048034667969s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 35.68231749534607s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.2032229900360107s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 89.31060028076172s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.6541357040405273s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.5354609489440918s
Security | Sign check for Norway fishery stocks dataset took 0.5303032398223877s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 10.552468299865723s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.3667411804199219s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.021352052688598633s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 3.9577484130859375e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 4.291534423828125e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 1.1682510375976562e-05s
INFO | --- Analysis for Norway_Fishery_ took 2249.8264927864075s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.25766777992248535s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.2707679271697998s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.021026611328125s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.7206878662109375e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.52587890625e-05s
INFO | --- Analysis for norwegian-geo-divisions took 6.038941144943237s
Availability | SPARQL endpoint availability check for NITP took 8.273124694824219e-05s
Availability | VoID file availability check for NITP took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for NITP took 0.2672462463378906s
Reputation | Calculation of the PageRank for NITP took 0.02101898193359375s
Interlinking | Calculation of Degree of Connection for NITP took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for NITP took 6.4849853515625e-05s
Believability | Calculation of trust value for NITP took 1.1444091796875e-05s
INFO | --- Analysis for notIdentifier took 2.9753870964050293s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 0.00010013580322265625s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.2680072784423828s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.020853757858276367s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.5762786865234375e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 1.0013580322265625e-05s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.673816680908203s
Availability | SPARQL endpoint availability check for NPM took 8.296966552734375e-05s
Availability | VoID file availability check for NPM took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for NPM took 0.2621419429779053s
Reputation | Calculation of the PageRank for NPM took 0.021088600158691406s
Interlinking | Calculation of Degree of Connection for NPM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for NPM took 3.457069396972656e-05s
Believability | Calculation of trust value for NPM took 1.0967254638671875e-05s
INFO | --- Analysis for npm took 3.179333448410034s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.031879425048828125s
Availability | VoID file availability check for NTNU special collections took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.26204514503479004s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020905733108520508s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.6743621826171875e-05s
Believability | Calculation of trust value for NTNU special collections took 1.0251998901367188e-05s
INFO | --- Analysis for ntnusc took 5.065526485443115s
Availability | SPARQL endpoint availability check for links took 9.393692016601562e-05s
Availability | VoID file availability check for links took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for links took 0.26634955406188965s
Reputation | Calculation of the PageRank for links took 0.020808696746826172s
Interlinking | Calculation of Degree of Connection for links took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for links took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for links took 1.2159347534179688e-05s
Believability | Calculation of trust value for links took 6.67572021484375e-06s
INFO | --- Analysis for nugmyanmar took 2.384706974029541s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 8.344650268554688e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.2682774066925049s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.584426879882812e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 8.58306884765625e-06s
INFO | --- Analysis for nuts-geovocab took 2.434267282485962s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.38010144233703613s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.27180051803588867s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.020998477935791016s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.651878356933594e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 1.0967254638671875e-05s
INFO | --- Analysis for nvd took 3.935346841812134s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 5.785005569458008s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.28099751472473145s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.021272659301757812s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 7.867813110351562e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.2874603271484375e-05s
INFO | --- Analysis for nvs took 13.419655323028564s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 8.034706115722656e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.00040340423583984375s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.26294755935668945s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.021615982055664062s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.0001857280731201172s
Believability | Calculation of trust value for New York Times - Linked Open Data took 9.059906005859375e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.459779977798462s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.5394721031188965s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0006861686706542969s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.398953914642334s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.754812479019165s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 5.176649570465088s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.6107428073883057s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 58.198729038238525s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.309292793273926s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.28249025344848633s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.3516533374786377s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.42363405227661133s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.46361231803894043s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.34978628158569336s
License | HR license check for Italian Chamber of Deputies - official dataset took 58.20902490615845s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.3555283546447754s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.9608955383300781s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.7203330993652344s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.40912842750549316s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.35634756088256836s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.319915771484375s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 10.895292520523071s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 0.00010633468627929688s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.35515904426574707s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.38344621658325195s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.3546719551086426s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.344846248626709s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.4210796356201172s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.7023882865905762s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.34789109230041504s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 16.838781118392944s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.3545515537261963s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.3162398338317871s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.35663390159606934s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.7343323230743408s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.03013324737548828s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.0282132625579834s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.34503722190856934s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 12.652832269668579s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.43297886848449707s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 1.823448896408081s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.1395204067230225s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 13.39933729171753s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03158164024353027s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.38271212577819824s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.3529644012451172s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 9.661616802215576s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.3015177249908447s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.022598743438720703s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00010204315185546875s
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.1205673217773438e-05s
INFO | --- Analysis for ocd took 380.57279682159424s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 8.940696716308594e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.27318739891052246s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.02055835723876953s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.838539123535156e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.1682510375976562e-05s
INFO | --- Analysis for oceandrilling-borehole took 3.1428027153015137s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 2.4450275897979736s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.26410746574401855s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.02065134048461914s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 7.987022399902344e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.1920928955078125e-05s
INFO | --- Analysis for oceandrilling-codices took 7.837080240249634s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 2.4272148609161377s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.26535606384277344s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.021886348724365234s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.409385681152344e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.239776611328125e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 6.842347621917725s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 2.7439658641815186s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.268218994140625s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.02243518829345703s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.62396240234375e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.2636184692382812e-05s
INFO | --- Analysis for oceandrilling-forams took 7.128307342529297s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 2.659891128540039s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0007863044738769531s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.2736244201660156s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.021384477615356445s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.8623809814453125e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.0013580322265625e-05s
INFO | --- Analysis for oceandrilling-janus took 7.02227520942688s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 12.27397346496582s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0011444091796875s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.26656627655029297s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.022974491119384766s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 4.172325134277344e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.0728836059570312e-05s
INFO | --- Analysis for oceandrilling-janusamp took 16.973005771636963s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.40495228767395s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.26340460777282715s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.021026611328125s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.170967102050781e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 6.198883056640625e-06s
INFO | --- Analysis for oceandrilling-ldeo took 6.788578510284424s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.315376281738281e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.26550912857055664s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.021869421005249023s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.841255187988281e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.0728836059570312e-05s
INFO | --- Analysis for oclc-fast took 8.239710569381714s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.1961669921875e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.26501035690307617s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0209808349609375s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.314018249511719e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 9.298324584960938e-06s
INFO | --- Analysis for odc-imd-environment-score took 5.860153913497925s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.12040948867797852s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0005602836608886719s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 1.1528587341308594s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 0.6619372367858887s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.1666879653930664s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.305466651916504s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.4719853401184082s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 30.21592879295349s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.09620046615600586s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.12734127044677734s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.19060540199279785s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 46.48467826843262s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.1214151382446289s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 30.130600452423096s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.1291968822479248s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.18860864639282227s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.3667304515838623s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.11887097358703613s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.13521575927734375s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.18197250366210938s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 10.75322961807251s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 6.651878356933594e-05s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.11963987350463867s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.18807005882263184s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.18036556243896484s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.1848433017730713s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.12016177177429199s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.38259077072143555s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.12055087089538574s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 3.642148971557617s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.1255052089691162s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.1961824893951416s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.12804818153381348s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.2001354694366455s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.6040990352630615s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 1.736725091934204s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.3539810180664062s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.00015783309936523438s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.6134903430938721s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.21483802795410156s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.2640647888183594s
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.71661376953125e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 9.059906005859375e-06s
INFO | --- Analysis for odc-lsoa took 263.53964495658875s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0921163558959961s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0002105236053466797s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.25753068923950195s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.846687316894531e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for oecd-linked-data took 2.4737839698791504s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.42549157142639s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.26818370819091797s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.839897155761719e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 6.4373016357421875e-06s
INFO | --- Analysis for ogolod took 102.83224892616272s
Availability | SPARQL endpoint availability check for OLAC Metadata took 4.100799560546875e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.2602360248565674s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.02078866958618164s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 4.38690185546875e-05s
Believability | Calculation of trust value for OLAC Metadata took 6.4373016357421875e-06s
INFO | --- Analysis for olac took 22.559760808944702s
Availability | SPARQL endpoint availability check for OLiA took 4.57763671875e-05s
Availability | VoID file availability check for OLiA took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for OLiA took 0.2634246349334717s
Reputation | Calculation of the PageRank for OLiA took 0.02031850814819336s
Interlinking | Calculation of Degree of Connection for OLiA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OLiA took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00012135505676269531s
Believability | Calculation of trust value for OLiA took 1.1444091796875e-05s
INFO | --- Analysis for olia took 12.917859077453613s
Availability | SPARQL endpoint availability check for OLiA Discourse took 0.00010442733764648438s
Availability | VoID file availability check for OLiA Discourse took 0.00035071372985839844s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.259960412979126s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 3.886222839355469e-05s
Believability | Calculation of trust value for OLiA Discourse took 5.9604644775390625e-06s
INFO | --- Analysis for olia-discourse took 7.095376491546631s
Availability | SPARQL endpoint availability check for Open Land Use took 0.17713212966918945s
Availability | VoID file availability check for Open Land Use took 0.0005431175231933594s
Extra | Recovery of all triples for Open Land Use took 112.06998562812805s
Performance | Total latancy measurement for Open Land Use took 0.8821916580200195s
Amount of data | Number of triples check for Open Land Use took 9.254647493362427s
Interoperability | New terms check for Open Land Use took 14.114848375320435s
Versatility | Languages check for Open Land Use took 300.2366895675659s
Interpretability | Number of blank nodes check for Open Land Use took 1.8821978569030762s
Interpretability | RDF structures check for Open Land Use took 0.20452427864074707s
Versatility | Serialization formats check for Open Land Use took 9.260559558868408s
Availability | RDF dump link check for Open Land Use took 0.21874594688415527s
License | MR license check for Open Land Use took 0.17869925498962402s
License | HR license check for Open Land Use took 300.1524512767792s
Amount of data | Number of property check for Open Land Use took 0.185272216796875s
Understandability | Number of label check for Open Land Use took 1.5328569412231445s
Understandability | URI regex check for Open Land Use took 0.9429175853729248s
Understandability | Vocabs check for Open Land Use took 0.2586178779602051s
Verifiability | Authors check for Open Land Use took 0.17940211296081543s
Verifiability | Publishers check for Open Land Use took 0.2390122413635254s
Performance | Throughput check for Open Land Use took 10.825445652008057s
Amount of data | Check the number of entities for Open Land Use took 6.914138793945312e-05s
Verifiability | Contribs. check for Open Land Use took 0.1785440444946289s
Interlinking | sameAs chians check for Open Land Use took 0.19250774383544922s
Interlinking | skos check for Open Land Use took 0.40857410430908203s
Interlinking | skos check for Open Land Use took 0.4154195785522461s
Timeliness | dataset update frequency check for Open Land Use took 5.012923240661621s
Currency | Creation date check for Open Land Use took 0.4434537887573242s
Currency | Modification date check for Open Land Use took 0.21962356567382812s
Rep.Conc. | URIs length for Open Land Use took 155.7076313495636s
Interoperability | New vocabularies check for Open Land Use took 1.430511474609375e-05s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.3224310874938965s
Accuracy | Check Functional Property for Open Land Use took 0.299971342086792s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.250840425491333s
Accuracy | Check Empty annotation labels for Open Land Use took 39.2569215297699s
Accuracy | Check White space in annotation for Open Land Use took 2.618439197540283s
Accuracy | Check Datatype consistency for Open Land Use took 2.5920257568359375s
Consistency | Disjoint class check for Open Land Use took 0.17347955703735352s
Consistency | Check Misplaced properties for Open Land Use took 87.19878935813904s
Consistency | Misplaced classes for Open Land Use took 8.387643337249756s
Consistency | Check Ontology hijacking for Open Land Use took 29.457563161849976s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.25054931640625s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 87.64101076126099s
Conciseness | Check Extensional conciseness for Open Land Use took 2.688645124435425s
Conciseness | Check Intensional conciseness for Open Land Use took 0.4976630210876465s
Security | Sign check for Open Land Use took 0.39402341842651367s
Availability | Check URIs Dereferenciability for Open Land Use took 9.35222578048706s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.5736489295959473s
Reputation | Calculation of the PageRank for Open Land Use took 0.021303653717041016s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 4.3392181396484375e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 5.4836273193359375e-06s
Believability | Calculation of trust value for Open Land Use took 1.2159347534179688e-05s
INFO | --- Analysis for OLU took 2226.295079469681s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.7984187602996826s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0003948211669921875s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.2633857727050781s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.02280259132385254s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 4.124641418457031e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-als took 3.6710360050201416s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.2830078601837158s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.27441859245300293s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.021208763122558594s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-arb took 3.140395402908325s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.24392104148864746s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0004076957702636719s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.2612578868865967s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.021172761917114258s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-bul took 2.997352123260498s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2412428855895996s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00041866302490234375s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.25665760040283203s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020426511764526367s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-cow took 2.9882655143737793s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.25753045082092285s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00042724609375s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.27223849296569824s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0224153995513916s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-cwn took 3.02321457862854s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.25487828254699707s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.00041556358337402344s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.2633020877838135s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.02139735221862793s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 4.172325134277344e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-dan took 3.0009918212890625s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.21968436241149902s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0004315376281738281s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.2676382064819336s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
INFO | --- Analysis for omwn-ell took 3.0187628269195557s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.25698184967041016s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2692129611968994s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.02112126350402832s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-eng took 3.081268310546875s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.24660587310791016s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.26955246925354004s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.02254652976989746s
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.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-fas took 3.1140873432159424s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.24893736839294434s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2627220153808594s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.021526336669921875s
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.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-fin took 3.0919480323791504s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.26795125007629395s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.2720456123352051s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.021056652069091797s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 4.649162292480469e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-fra took 3.0610084533691406s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.2358860969543457s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.27790331840515137s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0208740234375s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-heb took 3.036076068878174s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.24339914321899414s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0004215240478515625s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2705235481262207s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.020847797393798828s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-hrv took 3.0809881687164307s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.23824620246887207s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2682962417602539s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.021920204162597656s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 4.100799560546875e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
INFO | --- Analysis for omwn-isl took 3.0556745529174805s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.25081920623779297s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.00043201446533203125s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.28635215759277344s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.021358966827392578s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-ita took 3.065609931945801s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.2512705326080322s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.27170729637145996s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.022305965423583984s
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.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 2.09808349609375e-05s
INFO | --- Analysis for omwn-iwn took 3.046830892562866s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.24157118797302246s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.00041365623474121094s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.27062106132507324s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.021589279174804688s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-jpn took 3.0858144760131836s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.23061060905456543s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.00042557716369628906s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.2615039348602295s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.022568702697753906s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 4.315376281738281e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-mcr took 2.9927845001220703s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.22533655166625977s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0002033710479736328s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2607591152191162s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.021719932556152344s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-msa took 2.9690659046173096s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.25200891494750977s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.26392126083374023s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.021021604537963867s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-nld took 3.0956766605377197s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.24916744232177734s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.26006484031677246s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.020848989486694336s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-nor took 3.070570230484009s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.24705266952514648s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2578132152557373s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020925521850585938s
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.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-pol took 2.994422674179077s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.25464725494384766s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2698798179626465s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.021028995513916016s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
INFO | --- Analysis for omwn-por took 3.0502095222473145s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.230912446975708s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0004220008850097656s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2691824436187744s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.022034883499145508s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
INFO | --- Analysis for omwn-ron took 3.073354959487915s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.22452950477600098s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2637979984283447s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.021906137466430664s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 4.220008850097656e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-slk took 2.9817721843719482s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.2607436180114746s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.27258777618408203s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.02109551429748535s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 4.100799560546875e-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 3.0872700214385986s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2471303939819336s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.26697540283203125s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.02121281623840332s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-swe took 2.9953713417053223s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.23323512077331543s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.00021314620971679688s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2608377933502197s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.020664691925048828s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-tha took 2.957156181335449s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 3.6281392574310303s
Availability | VoID file availability check for OntoBeef Domain took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.27356624603271484s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.02066779136657715s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 5.173683166503906e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.0967254638671875e-05s
INFO | --- Analysis for ontobeef-domain took 25.620492935180664s
Availability | SPARQL endpoint availability check for Ontos News Portal took 8.440017700195312e-05s
Availability | VoID file availability check for Ontos News Portal took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.2656435966491699s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020776748657226562s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 8.96453857421875e-05s
Believability | Calculation of trust value for Ontos News Portal took 1.0251998901367188e-05s
INFO | --- Analysis for ontos-news-portal took 4.44893217086792s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 8.96453857421875e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.00040912628173828125s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.264634370803833s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.021518707275390625s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.266334533691406e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 1.0013580322265625e-05s
INFO | --- Analysis for ookaboo-rdf-dump took 2.5215680599212646s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.291534423828125e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.2680342197418213s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.021137475967407227s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 4.0531158447265625e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 1.33514404296875e-05s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 8.886463403701782s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 8.845329284667969e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.27181363105773926s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.02265763282775879s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 0.0002033710479736328s
Believability | Calculation of trust value for Open Data Euskadi took 7.867813110351562e-06s
INFO | --- Analysis for open-data-euskadi took 7.472874402999878s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 4.100799560546875e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.00032806396484375s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.29573583602905273s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.021053314208984375s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.0001087188720703125s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 7.3909759521484375e-06s
INFO | --- Analysis for open-data-risp took 209.06563234329224s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.1480259895324707s
Availability | VoID file availability check for Open Data Thesaurus took 0.0005154609680175781s
Extra | Recovery of all triples for Open Data Thesaurus took 1.0544695854187012s
Performance | Total latancy measurement for Open Data Thesaurus took 0.412003755569458s
Amount of data | Number of triples check for Open Data Thesaurus took 0.10246944427490234s
Interoperability | New terms check for Open Data Thesaurus took 1.2565398216247559s
Versatility | Languages check for Open Data Thesaurus took 0.10772371292114258s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.10279726982116699s
Security | Check HTTPS for Open Data Thesaurus took 0.2931387424468994s
Interpretability | RDF structures check for Open Data Thesaurus took 0.1011195182800293s
Versatility | Serialization formats check for Open Data Thesaurus took 0.10206198692321777s
Availability | RDF dump link check for Open Data Thesaurus took 0.9474594593048096s
License | MR license check for Open Data Thesaurus took 0.10098147392272949s
License | HR license check for Open Data Thesaurus took 0.07927918434143066s
Amount of data | Number of property check for Open Data Thesaurus took 0.10887002944946289s
Understandability | Number of label check for Open Data Thesaurus took 0.10448217391967773s
Understandability | URI regex check for Open Data Thesaurus took 0.15571188926696777s
Understandability | Vocabs check for Open Data Thesaurus took 0.10145831108093262s
Verifiability | Authors check for Open Data Thesaurus took 0.10194110870361328s
Verifiability | Publishers check for Open Data Thesaurus took 0.10057187080383301s
Performance | Throughput check for Open Data Thesaurus took 10.209967136383057s
Amount of data | Check the number of entities for Open Data Thesaurus took 7.367134094238281e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.10634732246398926s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.10214900970458984s
Interlinking | skos check for Open Data Thesaurus took 0.10361194610595703s
Interlinking | skos check for Open Data Thesaurus took 0.07912063598632812s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.08015108108520508s
Currency | Creation date check for Open Data Thesaurus took 0.1581130027770996s
Currency | Modification date check for Open Data Thesaurus took 0.200791597366333s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.4006986618041992s
Interoperability | New vocabularies check for Open Data Thesaurus took 0.8708698749542236s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.10190534591674805s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.0779423713684082s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.0781245231628418s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.1523284912109375s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.001104593276977539s
Consistency | Disjoint class check for Open Data Thesaurus took 0.07766985893249512s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.15922141075134277s
Consistency | Misplaced classes for Open Data Thesaurus took 0.07824921607971191s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.2897615432739258s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.2204334735870361s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.0001583099365234375s
Security | Sign check for Open Data Thesaurus took 0.08476591110229492s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.2695736885070801s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.020182132720947266s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0006833076477050781s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.630752563476562e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 0.41878795623779297s
Believability | Calculation of trust value for Open Data Thesaurus took 5.9604644775390625e-06s
INFO | --- Analysis for open-data-thesaurus took 69.02806615829468s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.38690185546875e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.2791781425476074s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.02129673957824707s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 7.271766662597656e-05s
Believability | Calculation of trust value for Open Election Data Project took 5.7220458984375e-06s
INFO | --- Analysis for open-election-data-project took 42.42094802856445s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 4.280435800552368s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0007588863372802734s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.27233386039733887s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.021901607513427734s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 9.131431579589844e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 9.298324584960938e-06s
INFO | --- Analysis for open-energy-info-wiki took 17.40846538543701s
Availability | SPARQL endpoint availability check for Open Library took 4.100799560546875e-05s
Availability | VoID file availability check for Open Library took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for Open Library took 0.27001357078552246s
Reputation | Calculation of the PageRank for Open Library took 0.02205944061279297s
Interlinking | Calculation of Degree of Connection for Open Library took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.842613220214844e-05s
Believability | Calculation of trust value for Open Library took 1.0013580322265625e-05s
INFO | --- Analysis for open-library took 9.536888599395752s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.17631053924560547s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0005495548248291016s
Extra | Recovery of all triples for Open Land Use @PSNC took 107.71258592605591s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.8836648464202881s
Amount of data | Number of triples check for Open Land Use @PSNC took 9.256970167160034s
Interoperability | New terms check for Open Land Use @PSNC took 14.054576873779297s
Versatility | Languages check for Open Land Use @PSNC took 300.2360153198242s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 2.0456035137176514s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.18524837493896484s
Versatility | Serialization formats check for Open Land Use @PSNC took 9.10810136795044s
Availability | RDF dump link check for Open Land Use @PSNC took 0.2898271083831787s
License | MR license check for Open Land Use @PSNC took 0.546205997467041s
License | HR license check for Open Land Use @PSNC took 300.1438591480255s
Amount of data | Number of property check for Open Land Use @PSNC took 0.18302702903747559s
Understandability | Number of label check for Open Land Use @PSNC took 2.0468523502349854s
Understandability | URI regex check for Open Land Use @PSNC took 0.7135186195373535s
Understandability | Vocabs check for Open Land Use @PSNC took 0.2435622215270996s
Verifiability | Authors check for Open Land Use @PSNC took 0.19009804725646973s
Verifiability | Publishers check for Open Land Use @PSNC took 0.22980976104736328s
Performance | Throughput check for Open Land Use @PSNC took 10.722719192504883s
Amount of data | Check the number of entities for Open Land Use @PSNC took 7.486343383789062e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.17947006225585938s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.18288946151733398s
Interlinking | skos check for Open Land Use @PSNC took 0.4514729976654053s
Interlinking | skos check for Open Land Use @PSNC took 0.40093326568603516s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 4.550185441970825s
Currency | Creation date check for Open Land Use @PSNC took 0.4131937026977539s
Currency | Modification date check for Open Land Use @PSNC took 0.23010921478271484s
Rep.Conc. | URIs length for Open Land Use @PSNC took 153.87843298912048s
Interoperability | New vocabularies check for Open Land Use @PSNC took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.1803150177001953s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.29042625427246094s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.3019120693206787s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 37.63861274719238s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.6378040313720703s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.5963222980499268s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.1748032569885254s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 86.85671997070312s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.22836685180664s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 28.230467081069946s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.1983816623687744s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 88.38781929016113s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.687006950378418s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.4650237560272217s
Security | Sign check for Open Land Use @PSNC took 0.9527370929718018s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 10.611896514892578s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.4686710834503174s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.021419763565063477s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 3.886222839355469e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.0967254638671875e-05s
INFO | --- Analysis for Open_Land_Use took 2222.847044944763s
Availability | SPARQL endpoint availability check for flyatlas took 1.045318603515625s
Availability | VoID file availability check for flyatlas took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for flyatlas took 0.2654407024383545s
Reputation | Calculation of the PageRank for flyatlas took 0.021156787872314453s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.0517578125e-05s
Believability | Calculation of trust value for flyatlas took 8.344650268554688e-06s
INFO | --- Analysis for openbiomed-flyatlas took 5.053693056106567s
Availability | SPARQL endpoint availability check for OpenCalais took 8.893013000488281e-05s
Availability | VoID file availability check for OpenCalais took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.27329015731811523s
Reputation | Calculation of the PageRank for OpenCalais took 0.021909713745117188s
Interlinking | Calculation of Degree of Connection for OpenCalais took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OpenCalais took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00011086463928222656s
Believability | Calculation of trust value for OpenCalais took 1.1205673217773438e-05s
INFO | --- Analysis for opencalais took 5.987009525299072s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 8.869171142578125e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.27167415618896484s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020638465881347656s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 8.440017700195312e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 8.106231689453125e-06s
INFO | --- Analysis for opencorporates took 2.6533493995666504s
Availability | SPARQL endpoint availability check for OpenCyc took 8.177757263183594e-05s
Availability | VoID file availability check for OpenCyc took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.2758157253265381s
Reputation | Calculation of the PageRank for OpenCyc took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010347366333007812s
Believability | Calculation of trust value for OpenCyc took 8.821487426757812e-06s
INFO | --- Analysis for opencyc took 2.4752731323242188s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 8.606910705566406e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.2670722007751465s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.02099895477294922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.504753112792969e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 3.1027770042419434s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 8.392333984375e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.27059221267700195s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.02156662940979004s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 2.944136142730713s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 8.20159912109375e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.26951098442077637s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.021396160125732422s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.25580096244812s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 9.632110595703125e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.2658052444458008s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.021907329559326172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.4249799251556396s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 9.179115295410156e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.2704184055328369s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020952224731445312s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.154142379760742s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 8.344650268554688e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.2657644748687744s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020609617233276367s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 4.78412389755249s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.00038051605224609375s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.2630195617675781s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 3.9129514694213867s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.2718021869659424s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.360494613647461s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.9591064453125e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.2770671844482422s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020999670028686523s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0010173320770263672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 5.157622575759888s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.601478576660156e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.2594575881958008s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020808935165405273s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 4.093736886978149s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.0531158447265625e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0003063678741455078s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.2782769203186035s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020706892013549805s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 3.035670280456543s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.887580871582031e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.00034427642822265625s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.26279211044311523s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.021939516067504883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0010776519775390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 5.054473876953125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 3.0665018558502197s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.00031828880310058594s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.25485873222351074s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.02073502540588379s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 2.9976460933685303s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.26117801666259766s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.02091693878173828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.325631856918335s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0004036426544189453s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.2691988945007324s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 4.255620241165161s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007152557373046875s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.2746608257293701s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.02080392837524414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.9992353916168213s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 8.368492126464844e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.27077746391296387s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.021544218063354492s
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.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.1929268836975098s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 8.487701416015625e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.00037789344787597656s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.2671377658843994s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.020884037017822266s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 3.065289258956909s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 5.3882598876953125e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.26337361335754395s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.021037817001342773s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.4032018184661865s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.00011038780212402344s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.2742319107055664s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.022932767868041992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.2683234214782715s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 8.559226989746094e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.273618221282959s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.021163225173950195s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 4.162293910980225s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.26390814781188965s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020966768264770508s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.6689300537109375e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 3.874594211578369s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 9.465217590332031e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.266721248626709s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020645618438720703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.00011134147644042969s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.892735481262207s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007579326629638672s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.27331066131591797s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020895004272460938s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0009524822235107422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 5.245208740234375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 3.6003928184509277s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007367134094238281s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.266324520111084s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.020423173904418945s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.696846008300781e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 3.536686897277832s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 8.535385131835938e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.26992106437683105s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0219423770904541s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.614328145980835s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.2692389488220215s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.020973682403564453s
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.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 3.649033546447754s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.26320719718933105s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.020696640014648438s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 3.17205548286438s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 9.322166442871094e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007505416870117188s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.26508474349975586s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.744529724121094e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.674791574478149s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.2664167881011963s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.022441864013671875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0010035037994384766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 5.2928924560546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 3.6158852577209473s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 8.702278137207031e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.27804064750671387s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020740985870361328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.838539123535156e-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 3.6774215698242188s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2775301933288574s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.02208423614501953s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 3.8616952896118164s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 8.58306884765625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.000823974609375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.27142977714538574s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.02078986167907715s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.57763671875e-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 3.2718188762664795s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.416175842285156e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.26824283599853516s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.022502660751342773s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.3913938999176025s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 8.988380432128906e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0010652542114257812s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.26482415199279785s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.02278614044189453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.744529724121094e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.4271955490112305s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0003688335418701172s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.2713346481323242s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.021306514739990234s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 5.030632019042969e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 3.628586530685425s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.2716042995452881s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.020876407623291016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 3.3254637718200684s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 8.893013000488281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007367134094238281s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.2676229476928711s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.02112126350402832s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.744529724121094e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 3.9540553092956543s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 8.392333984375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.27729129791259766s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.022485971450805664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0011661052703857422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 5.4836273193359375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 78.33984470367432s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 8.654594421386719e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.265167236328125s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.024640560150146484s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 5.435943603515625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 3.636927843093872s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 8.869171142578125e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0011909008026123047s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.26916933059692383s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020891189575195312s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.986933946609497s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.00037980079650878906s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.26511669158935547s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.022444486618041992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.184054374694824s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 8.678436279296875e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0003993511199951172s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.26239562034606934s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 3.858297824859619s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 5.205230712890625s
Availability | VoID file availability check for Open Data of Ecuador took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.27135133743286133s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.02321934700012207s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.130073547363281e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.3113021850585938e-05s
INFO | --- Analysis for opendataec took 10.477822065353394s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.57763671875e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.2625594139099121s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020903348922729492s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.2636184692382812e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 16.575908422470093s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 8.559226989746094e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.2688150405883789s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.02113056182861328s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 3.8488879203796387s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 9.012222290039062e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.00034165382385253906s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.2617654800415039s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.03375697135925293s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 9.775161743164062e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.446669816970825s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 8.273124694824219e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.27104759216308594s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020920515060424805s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 1.0013580322265625e-05s
INFO | --- Analysis for opendatascotland-simd-education-rank took 4.280968904495239s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 8.96453857421875e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.28690481185913086s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.020906686782836914s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.2159347534179688e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 3.8208186626434326s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 8.58306884765625e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.28740668296813965s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 4.76837158203125e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 1.2636184692382812e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 3.467357635498047s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.5009915828704834s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.020868539810180664s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 1.2636184692382812e-05s
INFO | --- Analysis for opendatascotland-simd-health-rank took 3.9555389881134033s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 8.511543273925781e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.27976441383361816s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020599842071533203s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 5.7220458984375e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 3.9801220893859863s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.410743713378906e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0010471343994140625s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.2650582790374756s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.021965980529785156s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.001171112060546875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 5.4836273193359375e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 1.2874603271484375e-05s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.4295506477355957s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.678639888763428s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.2729034423828125s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.021408796310424805s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 4.076957702636719e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.239776611328125e-05s
INFO | --- Analysis for openlink-lod-cache took 63.12824368476868s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 4.4345855712890625e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.265333890914917s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 8.940696716308594e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 1.0251998901367188e-05s
INFO | --- Analysis for openlinksw-dataspaces took 2.8924992084503174s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 8.797645568847656e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0007817745208740234s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.2673075199127197s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.02084064483642578s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.72747802734375e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 7.62939453125e-06s
INFO | --- Analysis for openlylocal took 12.04367733001709s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.2629990577697754s
Availability | VoID file availability check for OpenMobileNetwork took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.26347994804382324s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02089524269104004s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.033348083496094e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 8.106231689453125e-06s
INFO | --- Analysis for openmobilenetwork took 4.701259613037109s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.9116110801696777s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.001013040542602539s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.2796213626861572s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.489059448242188e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 1.1682510375976562e-05s
INFO | --- Analysis for ordnance-survey-linked-data took 5.343617677688599s
Availability | SPARQL endpoint availability check for oreilly took 4.291534423828125e-05s
Availability | VoID file availability check for oreilly took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for oreilly took 0.27347683906555176s
Reputation | Calculation of the PageRank for oreilly took 0.022939443588256836s
Interlinking | Calculation of Degree of Connection for oreilly took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for oreilly took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.6253204345703125e-05s
Believability | Calculation of trust value for oreilly took 1.0967254638671875e-05s
INFO | --- Analysis for oreilly took 5.342379093170166s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.659170389175415s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.26033473014831543s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.123283386230469e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 1.239776611328125e-05s
INFO | --- Analysis for Organchem-Data took 7.502808332443237s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.05121445655822754s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.2685232162475586s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020479440689086914s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 6.4849853515625e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.1205673217773438e-05s
INFO | --- Analysis for organic-edunet took 8.844000816345215s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.6050360202789307s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.00048470497131347656s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 6.287333965301514s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.9317994117736816s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.2104189395904541s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.4824333190917969s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 6.426229953765869s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.13837981224060059s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.3618292808532715s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.1272430419921875s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.1189568042755127s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.14919042587280273s
License | HR license check for Open Research Knowledge Graph (ORKG) took 3.936723470687866s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.15023303031921387s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.15777254104614258s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.25698161125183105s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.12172937393188477s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.12289762496948242s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.12193536758422852s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.794984340667725s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 0.00010657310485839844s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.15584325790405273s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.15038681030273438s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.16204214096069336s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.2084517478942871s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.1954643726348877s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.39125585556030273s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.4768257141113281s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 4.67593240737915s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.2112410068511963s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.316631555557251s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.23096394538879395s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 2.5079336166381836s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.28984546661376953s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.2663407325744629s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.30734682083129883s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.391282081604004s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.8434915542602539s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 3.110750913619995s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.1937897205352783s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 1.9246010780334473s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.28860974311828613s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.11998772621154785s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.1347804069519043s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 1841.6264276504517s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.4412517547607422s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.02086496353149414s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 2.0265579223632812e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 4.76837158203125e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.1205673217773438e-05s
INFO | --- Analysis for orkg took 2070.7407777309418s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.919067144393921s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.26470255851745605s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020987272262573242s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 9.322166442871094e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 1.0251998901367188e-05s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 28.2505886554718s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.4338912963867188s
Availability | VoID file availability check for OSM Semantic Network took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.2740135192871094s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.02102971076965332s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.7670135498046875e-05s
Believability | Calculation of trust value for OSM Semantic Network took 1.2636184692382812e-05s
INFO | --- Analysis for osm-semantic-network took 7.854987621307373s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.2997243404388428s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.00048542022705078125s
Extra | Recovery of all triples for Open Transport Map @PSNC took 119.307936668396s
Performance | Total latancy measurement for Open Transport Map @PSNC took 0.8844809532165527s
Amount of data | Number of triples check for Open Transport Map @PSNC took 9.061954736709595s
Interoperability | New terms check for Open Transport Map @PSNC took 14.164350986480713s
Versatility | Languages check for Open Transport Map @PSNC took 300.1844675540924s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 2.382336378097534s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.2479078769683838s
Versatility | Serialization formats check for Open Transport Map @PSNC took 9.421693325042725s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.26025867462158203s
License | MR license check for Open Transport Map @PSNC took 0.4718313217163086s
License | HR license check for Open Transport Map @PSNC took 300.2381896972656s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.1819748878479004s
Understandability | Number of label check for Open Transport Map @PSNC took 1.8329722881317139s
Understandability | URI regex check for Open Transport Map @PSNC took 0.49745655059814453s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.33718132972717285s
Verifiability | Authors check for Open Transport Map @PSNC took 0.18045949935913086s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.22880959510803223s
Performance | Throughput check for Open Transport Map @PSNC took 10.670804262161255s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 6.818771362304688e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.18024349212646484s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.18197107315063477s
Interlinking | skos check for Open Transport Map @PSNC took 0.4165952205657959s
Interlinking | skos check for Open Transport Map @PSNC took 0.4043116569519043s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 3.8322529792785645s
Currency | Creation date check for Open Transport Map @PSNC took 0.43619799613952637s
Currency | Modification date check for Open Transport Map @PSNC took 0.23053932189941406s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 150.5025656223297s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.1796262264251709s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.3248775005340576s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.3139331340789795s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 37.33809971809387s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.6309757232666016s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.6060824394226074s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.17651081085205078s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 86.03187274932861s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.485110998153687s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 35.86511993408203s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.2020304203033447s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 88.29613089561462s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.672527551651001s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.46300292015075684s
Security | Sign check for Open Transport Map @PSNC took 0.8235068321228027s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 10.252548933029175s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.4762992858886719s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.02136993408203125s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 4.553794860839844e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 1.1205673217773438e-05s
INFO | --- Analysis for OTM took 2235.774444580078s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 11.699414730072021s
Availability | VoID file availability check for Pali English Lexicon took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.26598548889160156s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.022075891494750977s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 4.3392181396484375e-05s
Believability | Calculation of trust value for Pali English Lexicon took 3.337860107421875e-05s
INFO | --- Analysis for pali-english-lexicon took 28.442291736602783s
Availability | SPARQL endpoint availability check for PanLex took 1.7960739135742188s
Availability | VoID file availability check for PanLex took 0.0003628730773925781s
Completeness | Calculation of interlinking completeness for PanLex took 0.2638869285583496s
Reputation | Calculation of the PageRank for PanLex took 0.022481441497802734s
Interlinking | Calculation of Degree of Connection for PanLex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.653236389160156e-05s
Believability | Calculation of trust value for PanLex took 1.2159347534179688e-05s
INFO | --- Analysis for panlex took 4.207019090652466s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.3392181396484375e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.2643711566925049s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020693540573120117s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.743171691894531e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.2159347534179688e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.0524091720581055s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.07935690879821777s
Availability | VoID file availability check for patents.data.gov.uk took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.2656691074371338s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 5.0067901611328125e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 1.0013580322265625e-05s
INFO | --- Analysis for patents-data-gov-uk took 2.5304276943206787s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 0.00010561943054199219s
Availability | VoID file availability check for PDEV-Lemon took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.2639803886413574s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.8623809814453125e-05s
Believability | Calculation of trust value for PDEV-Lemon took 1.1682510375976562e-05s
INFO | --- Analysis for pdev-lemon took 3.5601513385772705s
Availability | SPARQL endpoint availability check for pdevlemon took 8.273124694824219e-05s
Availability | VoID file availability check for pdevlemon took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.26692938804626465s
Reputation | Calculation of the PageRank for pdevlemon took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.4332275390625e-05s
Believability | Calculation of trust value for pdevlemon took 1.1682510375976562e-05s
INFO | --- Analysis for pdevlemon took 3.124678373336792s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.1961669921875e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0008420944213867188s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.2635152339935303s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.02081608772277832s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 7.724761962890625e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 7.3909759521484375e-06s
INFO | --- Analysis for periodo took 18.602275848388672s
Availability | SPARQL endpoint availability check for Personal_Homepages took 8.869171142578125e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.26361894607543945s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.000385284423828125s
Believability | Calculation of trust value for Personal_Homepages took 1.2636184692382812e-05s
INFO | --- Analysis for personal-homepages took 2.409292221069336s
Availability | SPARQL endpoint availability check for Ontology of University People took 5.7220458984375e-05s
Availability | VoID file availability check for Ontology of University People took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.26401567459106445s
Reputation | Calculation of the PageRank for Ontology of University People took 0.02127552032470703s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.00102996826171875s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 4.100799560546875e-05s
Believability | Calculation of trust value for Ontology of University People took 1.2636184692382812e-05s
INFO | --- Analysis for PersonOnto took 2.3991503715515137s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 5.445935487747192s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.26412391662597656s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020827054977416992s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1444091796875e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1682510375976562e-05s
INFO | --- Analysis for PFKHS took 9.459432125091553s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 3.255995035171509s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2642061710357666s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020950794219970703s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1444091796875e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.0251998901367188e-05s
INFO | --- Analysis for PFRPPH took 8.014459371566772s
Availability | SPARQL endpoint availability check for PGxLOD took 0.3667135238647461s
Availability | VoID file availability check for PGxLOD took 0.0006048679351806641s
Extra | Recovery of all triples for PGxLOD took 1.6648330688476562s
Performance | Total latancy measurement for PGxLOD took 0.7466957569122314s
Amount of data | Number of triples check for PGxLOD took 1.287278413772583s
Interoperability | New terms check for PGxLOD took 2.3708221912384033s
Versatility | Languages check for PGxLOD took 60.51328635215759s
Interpretability | Number of blank nodes check for PGxLOD took 1.8422956466674805s
Interpretability | RDF structures check for PGxLOD took 0.4810965061187744s
Versatility | Serialization formats check for PGxLOD took 0.3088843822479248s
Availability | RDF dump link check for PGxLOD took 14.252198934555054s
License | MR license check for PGxLOD took 0.7278046607971191s
License | HR license check for PGxLOD took 63.818349838256836s
Amount of data | Number of property check for PGxLOD took 0.1580829620361328s
Understandability | Number of label check for PGxLOD took 1.7773432731628418s
Understandability | URI regex check for PGxLOD took 0.4102287292480469s
Understandability | Vocabs check for PGxLOD took 0.3321201801300049s
Verifiability | Authors check for PGxLOD took 0.448472261428833s
Verifiability | Publishers check for PGxLOD took 0.2987549304962158s
Performance | Throughput check for PGxLOD took 10.45000696182251s
Amount of data | Check the number of entities for PGxLOD took 0.12266826629638672s
Verifiability | Contribs. check for PGxLOD took 0.15298843383789062s
Interlinking | sameAs chians check for PGxLOD took 0.2575070858001709s
Interlinking | skos check for PGxLOD took 1.567948341369629s
Interlinking | skos check for PGxLOD took 0.18498969078063965s
Timeliness | dataset update frequency check for PGxLOD took 0.36054515838623047s
Currency | Creation date check for PGxLOD took 0.5160708427429199s
Currency | Modification date check for PGxLOD took 0.31801414489746094s
Rep.Conc. | URIs length for PGxLOD took 6.598522901535034s
Interoperability | New vocabularies check for PGxLOD took 7.8981406688690186s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.15404701232910156s
Accuracy | Check Functional Property for PGxLOD took 0.18197989463806152s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.18927574157714844s
Accuracy | Check Empty annotation labels for PGxLOD took 0.9217617511749268s
Accuracy | Check White space in annotation for PGxLOD took 0.03710508346557617s
Accuracy | Check Datatype consistency for PGxLOD took 0.028792858123779297s
Consistency | Disjoint class check for PGxLOD took 0.2914109230041504s
Consistency | Check Misplaced properties for PGxLOD took 6.491239070892334s
Consistency | Misplaced classes for PGxLOD took 0.27840590476989746s
Consistency | Check Ontology hijacking for PGxLOD took 1.7724599838256836s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.1361000537872314s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 6.972735643386841s
Conciseness | Check Extensional conciseness for PGxLOD took 0.03260040283203125s
Conciseness | Check Intensional conciseness for PGxLOD took 0.2553398609161377s
Security | Sign check for PGxLOD took 0.16192078590393066s
Availability | Check URIs Dereferenciability for PGxLOD took 2185.3078615665436s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.5907416343688965s
Reputation | Calculation of the PageRank for PGxLOD took 0.021192550659179688s
Interlinking | Calculation of Degree of Connection for PGxLOD took 6.890296936035156e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0008099079132080078s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 0.00010442733764648438s
Interoperability | Check the re-using of existing vocabs for PGxLOD took 11.17967176437378s
Believability | Calculation of trust value for PGxLOD took 1.2159347534179688e-05s
INFO | --- Analysis for PGxLOD took 3396.4295539855957s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.9583182334899902s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.2625846862792969s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.021155595779418945s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 4.315376281738281e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 5.9604644775390625e-06s
INFO | --- Analysis for phoible took 4.559262037277222s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 4.315376281738281e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.26790833473205566s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.02190566062927246s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 2.956390380859375e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 1.1205673217773438e-05s
INFO | --- Analysis for PISM took 13.996215105056763s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.1961669921875e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.27117085456848145s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.022087812423706055s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 9.655952453613281e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 1.0967254638671875e-05s
INFO | --- Analysis for planetdata-project-wiki took 2.470696449279785s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.1919505596160889s
Availability | VoID file availability check for digitized plant specimen took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.2633059024810791s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.0222320556640625s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 7.224082946777344e-05s
Believability | Calculation of trust value for digitized plant specimen took 1.2159347534179688e-05s
INFO | --- Analysis for plant-specimen took 3.6007211208343506s
Availability | SPARQL endpoint availability check for Pleiades took 8.893013000488281e-05s
Availability | VoID file availability check for Pleiades took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Pleiades took 0.26853060722351074s
Reputation | Calculation of the PageRank for Pleiades took 0.020975351333618164s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0009746551513671875s
Interlinking | Calculation of Clustering coefficient for Pleiades took 0.00011157989501953125s
Believability | Calculation of trust value for Pleiades took 9.5367431640625e-06s
INFO | --- Analysis for pleiades took 10.489905834197998s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 0.0001385211944580078s
Availability | VoID file availability check for podorozhnyk.com took 0.0007886886596679688s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.274097204208374s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020504474639892578s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 2.9802322387695312e-05s
Believability | Calculation of trust value for podorozhnyk.com took 1.1682510375976562e-05s
INFO | --- Analysis for podorozhnyk took 3.080162525177002s
Availability | SPARQL endpoint availability check for Poképédia took 8.273124694824219e-05s
Availability | VoID file availability check for Poképédia took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2735481262207031s
Reputation | Calculation of the PageRank for Poképédia took 0.021782636642456055s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.081031799316406e-05s
Believability | Calculation of trust value for Poképédia took 1.0013580322265625e-05s
INFO | --- Analysis for pokepedia-fr took 2.576033115386963s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 8.630752563476562e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.26400184631347656s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.021017074584960938s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.772445678710938e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0251998901367188e-05s
INFO | --- Analysis for polymath-virtual-library took 5.598249197006226s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2444932460784912s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0005552768707275391s
Extra | Recovery of all triples for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 12.67241382598877s
Performance | Total latancy measurement for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.5937058925628662s
Amount of data | Number of triples check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.7309963703155518s
Interoperability | New terms check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.5377163887023926s
Versatility | Languages check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.5404386520385742s
Interpretability | Number of blank nodes check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.5564782619476318s
Interpretability | RDF structures check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11938619613647461s
Versatility | Serialization formats check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11781430244445801s
Availability | RDF dump link check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12314343452453613s
License | MR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12066054344177246s
License | HR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6105549335479736s
Amount of data | Number of property check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11372113227844238s
Understandability | Number of label check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.16565871238708496s
Understandability | URI regex check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.25698256492614746s
Understandability | Vocabs check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11455106735229492s
Verifiability | Authors check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.132171630859375s
Verifiability | Publishers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11542630195617676s
Performance | Throughput check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.836972951889038s
Amount of data | Check the number of entities for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 7.176399230957031e-05s
Verifiability | Contribs. check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11527180671691895s
Interlinking | sameAs chians check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11420989036560059s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11460185050964355s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11349797248840332s
Timeliness | dataset update frequency check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11483621597290039s
Currency | Creation date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.22771191596984863s
Currency | Modification date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2293078899383545s
Rep.Conc. | URIs length for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.442646026611328s
Interoperability | New vocabularies check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11615681648254395s
Accuracy | Check Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11336016654968262s
Accuracy | Check Inverse Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11273455619812012s
Accuracy | Check Empty annotation labels for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.2675998210906982s
Accuracy | Check White space in annotation for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.19275355339050293s
Accuracy | Check Datatype consistency for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.748983144760132s
Consistency | Disjoint class check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11460065841674805s
Consistency | Check Misplaced properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.8637535572052002s
Consistency | Check Ontology hijacking for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.045546293258667s
Consistency | Check Invalid usage of undefined classes for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.1273722648620605s
Consistency | Check Invalid usage of undefined properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.9536259174346924s
Conciseness | Check Extensional conciseness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.4117825031280518s
Security | Sign check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11287713050842285s
Availability | Check URIs Dereferenciability for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 4646.879170894623s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.6373798847198486s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.021316051483154297s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0008273124694824219s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.0265579223632812e-05s
Interoperability | Check the re-using of existing vocabs for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.9073486328125e-06s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.0967254638671875e-05s
INFO | --- Analysis for portuguese_prisons_releases took 4718.842685699463s
Availability | SPARQL endpoint availability check for prefix.cc took 9.703636169433594e-05s
Availability | VoID file availability check for prefix.cc took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.2696726322174072s
Reputation | Calculation of the PageRank for prefix.cc took 0.023112058639526367s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 4.029273986816406e-05s
Believability | Calculation of trust value for prefix.cc took 1.0013580322265625e-05s
INFO | --- Analysis for prefix-cc took 3.0382211208343506s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.4644920825958252s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.2612433433532715s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.020809650421142578s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.982948303222656e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.1444091796875e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 7.250234365463257s
Availability | SPARQL endpoint availability check for PreLex took 6.731573820114136s
Availability | VoID file availability check for PreLex took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for PreLex took 0.26587581634521484s
Reputation | Calculation of the PageRank for PreLex took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for PreLex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for PreLex took 6.937980651855469e-05s
Believability | Calculation of trust value for PreLex took 1.3113021850585938e-05s
INFO | --- Analysis for prelex took 18.161118507385254s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.36435604095459s
Availability | VoID file availability check for Prelinger Archives took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.2845470905303955s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020832061767578125s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.0279159545898438e-05s
Believability | Calculation of trust value for Prelinger Archives took 3.62396240234375e-05s
INFO | --- Analysis for prelinger_archives took 11.663288831710815s
Availability | SPARQL endpoint availability check for PreMOn took 0.26068758964538574s
Availability | VoID file availability check for PreMOn took 0.0006952285766601562s
Extra | Recovery of all triples for PreMOn took 5.208105802536011s
Performance | Total latancy measurement for PreMOn took 0.6057651042938232s
Amount of data | Number of triples check for PreMOn took 0.2905454635620117s
Interoperability | New terms check for PreMOn took 1.8078222274780273s
Versatility | Languages check for PreMOn took 59.01663613319397s
Interpretability | Number of blank nodes check for PreMOn took 0.13932085037231445s
Security | Check HTTPS for PreMOn took 0.07735037803649902s
Interpretability | RDF structures check for PreMOn took 0.1605074405670166s
Versatility | Serialization formats check for PreMOn took 0.1874992847442627s
Availability | RDF dump link check for PreMOn took 0.14908385276794434s
License | MR license check for PreMOn took 0.3303685188293457s
License | HR license check for PreMOn took 0.8989343643188477s
Amount of data | Number of property check for PreMOn took 0.17800521850585938s
Understandability | Number of label check for PreMOn took 0.6761167049407959s
Understandability | URI regex check for PreMOn took 0.3024733066558838s
Understandability | Vocabs check for PreMOn took 0.24696063995361328s
Verifiability | Authors check for PreMOn took 0.14312434196472168s
Verifiability | Publishers check for PreMOn took 0.23909258842468262s
Performance | Throughput check for PreMOn took 10.963191032409668s
Amount of data | Check the number of entities for PreMOn took 0.00011229515075683594s
Verifiability | Contribs. check for PreMOn took 0.15290570259094238s
Interlinking | sameAs chians check for PreMOn took 0.14768147468566895s
Interlinking | skos check for PreMOn took 0.252758264541626s
Interlinking | skos check for PreMOn took 0.12650489807128906s
Timeliness | dataset update frequency check for PreMOn took 0.1428232192993164s
Currency | Creation date check for PreMOn took 0.3150033950805664s
Currency | Modification date check for PreMOn took 0.305067777633667s
Rep.Conc. | URIs length for PreMOn took 3.874682664871216s
Interoperability | New vocabularies check for PreMOn took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for PreMOn took 0.4448838233947754s
Accuracy | Check Functional Property for PreMOn took 1.0597467422485352s
Accuracy | Check Inverse Functional Property for PreMOn took 0.9797036647796631s
Accuracy | Check Empty annotation labels for PreMOn took 1.2781500816345215s
Accuracy | Check White space in annotation for PreMOn took 0.07963848114013672s
Accuracy | Check Datatype consistency for PreMOn took 0.08205914497375488s
Consistency | Disjoint class check for PreMOn took 0.15015053749084473s
Consistency | Check Misplaced properties for PreMOn took 1.8425111770629883s
Consistency | Misplaced classes for PreMOn took 0.3926551342010498s
Consistency | Check Ontology hijacking for PreMOn took 2.546065092086792s
Consistency | Check Invalid usage of undefined classes for PreMOn took 1.1457064151763916s
Consistency | Check Invalid usage of undefined properties for PreMOn took 2.810436964035034s
Conciseness | Check Extensional conciseness for PreMOn took 0.0884394645690918s
Conciseness | Check Intensional conciseness for PreMOn took 0.16728568077087402s
Security | Sign check for PreMOn took 0.15826153755187988s
Availability | Check URIs Dereferenciability for PreMOn took 1087.7296056747437s
Completeness | Calculation of interlinking completeness for PreMOn took 0.29983973503112793s
Reputation | Calculation of the PageRank for PreMOn took 0.021070003509521484s
Interlinking | Calculation of Degree of Connection for PreMOn took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for PreMOn took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for PreMOn took 6.341934204101562e-05s
Interoperability | Check the re-using of existing vocabs for PreMOn took 2.1457672119140625e-06s
Believability | Calculation of trust value for PreMOn took 1.1682510375976562e-05s
INFO | --- Analysis for premon took 1212.6134357452393s
Availability | SPARQL endpoint availability check for Previsible took 4.220008850097656e-05s
Availability | VoID file availability check for Previsible took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Previsible took 0.2682793140411377s
Reputation | Calculation of the PageRank for Previsible took 0.020946025848388672s
Interlinking | Calculation of Degree of Connection for Previsible took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.2636184692382812e-05s
Believability | Calculation of trust value for Previsible took 1.1205673217773438e-05s
INFO | --- Analysis for Previsible took 2.4743425846099854s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 8.487701416015625e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.2702970504760742s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.698204040527344e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 1.0967254638671875e-05s
INFO | --- Analysis for princeton-library-findingaids took 3.5864098072052s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.5227241516113281s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0004260540008544922s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.26969456672668457s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020733356475830078s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 4.2438507080078125e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for PrinParLat took 4.313302040100098s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.2479238510131836s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.2710723876953125s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.021184921264648438s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.392333984375e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.3828277587890625e-05s
INFO | --- Analysis for printed-book-auction-catalogues took 3.022606134414673s
Availability | SPARQL endpoint availability check for Prior Panel took 8.678436279296875e-05s
Availability | VoID file availability check for Prior Panel took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.26148271560668945s
Reputation | Calculation of the PageRank for Prior Panel took 0.020943403244018555s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.528594970703125e-05s
Believability | Calculation of trust value for Prior Panel took 1.0967254638671875e-05s
INFO | --- Analysis for Prior_Panel took 2.4345691204071045s
Availability | SPARQL endpoint availability check for ProductDB took 1.1182219982147217s
Availability | VoID file availability check for ProductDB took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for ProductDB took 0.270418643951416s
Reputation | Calculation of the PageRank for ProductDB took 0.02108287811279297s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.534027099609375e-05s
Believability | Calculation of trust value for ProductDB took 1.1444091796875e-05s
INFO | --- Analysis for productdb took 4.11061692237854s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Product Types Ontology took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.26145076751708984s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.02108168601989746s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.534027099609375e-05s
Believability | Calculation of trust value for Product Types Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for productontology took 3.341078281402588s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.6253204345703125e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0007166862487792969s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.29398345947265625s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.02090764045715332s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010228157043457031s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.2159347534179688e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 7.21831750869751s
Availability | SPARQL endpoint availability check for provenanceweb took 0.045359134674072266s
Availability | VoID file availability check for provenanceweb took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.2728149890899658s
Reputation | Calculation of the PageRank for provenanceweb took 0.022545814514160156s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 6.914138793945312e-05s
Believability | Calculation of trust value for provenanceweb took 1.049041748046875e-05s
INFO | --- Analysis for provenanceweb took 47.41262245178223s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 8.702278137207031e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2634463310241699s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.02102518081665039s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 9.679794311523438e-05s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.3113021850585938e-05s
INFO | --- Analysis for proyectoapadrina took 7.420572280883789s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.075523138046265s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0009534358978271484s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.2695474624633789s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.021396875381469727s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.62396240234375e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 8.58306884765625e-06s
INFO | --- Analysis for pscs-catalogue took 123.9607036113739s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 8.559226989746094e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.26567625999450684s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.200241088867188e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 1.3113021850585938e-05s
INFO | --- Analysis for psh-subject-headings took 2.864253282546997s
Availability | SPARQL endpoint availability check for Depression took 0.4008166790008545s
Availability | VoID file availability check for Depression took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Depression took 0.26183605194091797s
Reputation | Calculation of the PageRank for Depression took 0.022104501724243164s
Interlinking | Calculation of Degree of Connection for Depression took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Depression took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Depression took 3.0517578125e-05s
Believability | Calculation of trust value for Depression took 1.2159347534179688e-05s
INFO | --- Analysis for Psychology took 2.841435194015503s
Availability | SPARQL endpoint availability check for PubChem RDF took 8.511543273925781e-05s
Availability | VoID file availability check for PubChem RDF took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.27016758918762207s
Reputation | Calculation of the PageRank for PubChem RDF took 0.021136760711669922s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0009257793426513672s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.482269287109375e-05s
Believability | Calculation of trust value for PubChem RDF took 1.0728836059570312e-05s
INFO | --- Analysis for PubChem_RDF took 5.303398132324219s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 60.03424382209778s
Availability | VoID file availability check for Public Spending in Greece took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.32987499237060547s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020977497100830078s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 7.62939453125e-05s
Believability | Calculation of trust value for Public Spending in Greece took 1.1682510375976562e-05s
INFO | --- Analysis for public-spending-in-greece took 146.91611766815186s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.2086200714111328s
Availability | VoID file availability check for Publications Office Authority tables took 0.0006079673767089844s
Extra | Recovery of all triples for Publications Office Authority tables took 173.31886625289917s
Performance | Total latancy measurement for Publications Office Authority tables took 0.5709817409515381s
Amount of data | Number of triples check for Publications Office Authority tables took 135.66121196746826s
Interoperability | New terms check for Publications Office Authority tables took 62.55982303619385s
Versatility | Languages check for Publications Office Authority tables took 300.0672290325165s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 22.144174814224243s
Security | Check HTTPS for Publications Office Authority tables took 0.323272705078125s
Interpretability | RDF structures check for Publications Office Authority tables took 0.41137099266052246s
Versatility | Serialization formats check for Publications Office Authority tables took 3.502154588699341s
Availability | RDF dump link check for Publications Office Authority tables took 0.1869049072265625s
License | MR license check for Publications Office Authority tables took 0.23955726623535156s
License | HR license check for Publications Office Authority tables took 300.0102984905243s
Amount of data | Number of property check for Publications Office Authority tables took 0.18006324768066406s
Understandability | Number of label check for Publications Office Authority tables took 1.592881202697754s
Understandability | URI regex check for Publications Office Authority tables took 0.3837888240814209s
Understandability | Vocabs check for Publications Office Authority tables took 0.09541726112365723s
Verifiability | Authors check for Publications Office Authority tables took 0.23900818824768066s
Verifiability | Publishers check for Publications Office Authority tables took 0.1976032257080078s
Performance | Throughput check for Publications Office Authority tables took 10.701712131500244s
Amount of data | Check the number of entities for Publications Office Authority tables took 6.842613220214844e-05s
Verifiability | Contribs. check for Publications Office Authority tables took 0.1504983901977539s
Interlinking | sameAs chians check for Publications Office Authority tables took 7.300785064697266s
Interlinking | skos check for Publications Office Authority tables took 0.17732691764831543s
Interlinking | skos check for Publications Office Authority tables took 0.14879226684570312s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.2824854850769043s
Currency | Creation date check for Publications Office Authority tables took 0.42464613914489746s
Currency | Modification date check for Publications Office Authority tables took 0.15756964683532715s
Rep.Conc. | URIs length for Publications Office Authority tables took 495.45368099212646s
Interoperability | New vocabularies check for Publications Office Authority tables took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.1584644317626953s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.22071170806884766s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.16719603538513184s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 40.623685121536255s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.144106149673462s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.540489673614502s
Consistency | Disjoint class check for Publications Office Authority tables took 0.12865686416625977s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.4873278141022s
Consistency | Misplaced classes for Publications Office Authority tables took 8.368991136550903s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 47.24690508842468s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.5905559062957764s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.3329350948334s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 2.967470407485962s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.363569974899292s
Security | Sign check for Publications Office Authority tables took 0.449063777923584s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 10.782914161682129s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 0.6906602382659912s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.02142047882080078s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 9.369850158691406e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.6689300537109375e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 9.059906005859375e-06s
INFO | --- Analysis for publications_office_authority_tables took 14388.268758058548s
Availability | SPARQL endpoint availability check for QBOAirbase took 8.392333984375e-05s
Availability | VoID file availability check for QBOAirbase took 0.0007641315460205078s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.2799196243286133s
Reputation | Calculation of the PageRank for QBOAirbase took 0.02072930335998535s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.891654968261719e-05s
Believability | Calculation of trust value for QBOAirbase took 1.0251998901367188e-05s
INFO | --- Analysis for qboairbase took 136.1034598350525s
Availability | SPARQL endpoint availability check for Qualité de l'air took 8.96453857421875e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.2606968879699707s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.022205591201782227s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 2.86102294921875e-05s
Believability | Calculation of trust value for Qualité de l'air took 9.5367431640625e-06s
INFO | --- Analysis for Qualité_de_l'air took 2.7853024005889893s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 8.654594421386719e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.27399492263793945s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.021071910858154297s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.62396240234375e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 1.0251998901367188e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 52.02476501464844s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.49915003776550293s
Availability | VoID file availability check for Querolus in LiLa took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.28714704513549805s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.02079176902770996s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.600120544433594e-05s
Believability | Calculation of trust value for Querolus in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for Querolus took 4.044487714767456s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.35348081588745117s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0006630420684814453s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 30.13725972175598s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.6924653053283691s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.361053943634033s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.6811397075653076s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.772323608398438s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.411198377609253s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12941551208496094s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15450239181518555s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12930774688720703s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1309342384338379s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15176010131835938s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13225317001342773s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1314241886138916s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2642631530761719s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12939810752868652s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13283514976501465s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13053536415100098s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.619266271591187s
Amount of data | Check the number of entities for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.176399230957031e-05s
Verifiability | Contribs. check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12947583198547363s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12892484664916992s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1319429874420166s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13143038749694824s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12974929809570312s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2621591091156006s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.26042962074279785s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 21.040534496307373s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12808012962341309s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13464927673339844s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1287529468536377s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13157987594604492s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.814697265625e-05s
Accuracy | Check Datatype consistency for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.066002130508423s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15691900253295898s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.493194103240967s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.697449684143066s
Consistency | Check Invalid usage of undefined classes for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.2247259616851807s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.473664283752441s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.759335994720459s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12734341621398926s
Availability | Check URIs Dereferenciability for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 14.467849016189575s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.3535134792327881s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.020679473876953125s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.430511474609375e-06s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.62939453125e-06s
INFO | --- Analysis for racai-legalnero took 159.1292028427124s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 8.821487426757812e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.30416345596313477s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.021466493606567383s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 2.7894973754882812e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 1.1205673217773438e-05s
INFO | --- Analysis for racai-llod-corola-we took 2.829981803894043s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.15036630630493164s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0005960464477539062s
Extra | Recovery of all triples for PARSEME-Ro corpus took 30.411694765090942s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.6480212211608887s
Amount of data | Number of triples check for PARSEME-Ro corpus took 6.765907049179077s
Interoperability | New terms check for PARSEME-Ro corpus took 1.9755818843841553s
Versatility | Languages check for PARSEME-Ro corpus took 18.26815128326416s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.3007800579071045s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.13088440895080566s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.13342952728271484s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.1300950050354004s
License | MR license check for PARSEME-Ro corpus took 0.14536786079406738s
License | HR license check for PARSEME-Ro corpus took 10.14284348487854s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.12946176528930664s
Understandability | Number of label check for PARSEME-Ro corpus took 0.18904423713684082s
Understandability | URI regex check for PARSEME-Ro corpus took 0.2578847408294678s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.12964606285095215s
Verifiability | Authors check for PARSEME-Ro corpus took 0.13053393363952637s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.13004779815673828s
Performance | Throughput check for PARSEME-Ro corpus took 10.425518274307251s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 0.00013017654418945312s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.13192176818847656s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 10.077667713165283s
Interlinking | skos check for PARSEME-Ro corpus took 10.003870248794556s
Interlinking | skos check for PARSEME-Ro corpus took 10.096762657165527s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 9.998920440673828s
Currency | Creation date check for PARSEME-Ro corpus took 20.000101327896118s
Currency | Modification date check for PARSEME-Ro corpus took 11.222824335098267s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 78.88824701309204s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.1450514793395996s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.14319729804992676s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.14414215087890625s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 2.694793701171875s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.23291563987731934s
Accuracy | Check Datatype consistency for PARSEME-Ro corpus took 4.094003677368164s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.145704984664917s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 10.943151473999023s
Consistency | Check Ontology hijacking for PARSEME-Ro corpus took 27.835251331329346s
Consistency | Check Invalid usage of undefined classes for PARSEME-Ro corpus took 1.4881236553192139s
Consistency | Check Invalid usage of undefined properties for PARSEME-Ro corpus took 12.943795204162598s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 2.793776512145996s
Security | Sign check for PARSEME-Ro corpus took 0.1485750675201416s
Availability | Check URIs Dereferenciability for PARSEME-Ro corpus took 7.427975654602051s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.4008960723876953s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0006825923919677734s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.170967102050781e-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 6.9141387939453125e-06s
INFO | --- Analysis for racai-llod-parseme-ro took 345.5196478366852s
Availability | SPARQL endpoint availability check for RoLEX took 0.146087646484375s
Availability | VoID file availability check for RoLEX took 0.0005702972412109375s
Extra | Recovery of all triples for RoLEX took 37.0777862071991s
Performance | Total latancy measurement for RoLEX took 0.6641228199005127s
Amount of data | Number of triples check for RoLEX took 1.6451773643493652s
Interoperability | New terms check for RoLEX took 1.553776502609253s
Versatility | Languages check for RoLEX took 4.095174551010132s
Interpretability | Number of blank nodes check for RoLEX took 1.04386305809021s
Interpretability | RDF structures check for RoLEX took 0.13119149208068848s
Versatility | Serialization formats check for RoLEX took 0.12947845458984375s
Availability | RDF dump link check for RoLEX took 0.13041234016418457s
License | MR license check for RoLEX took 0.13167548179626465s
License | HR license check for RoLEX took 0.1348567008972168s
Amount of data | Number of property check for RoLEX took 0.13402628898620605s
Understandability | Number of label check for RoLEX took 0.13400864601135254s
Understandability | URI regex check for RoLEX took 0.2835559844970703s
Understandability | Vocabs check for RoLEX took 0.13248801231384277s
Verifiability | Authors check for RoLEX took 0.13504457473754883s
Verifiability | Publishers check for RoLEX took 0.13362526893615723s
Performance | Throughput check for RoLEX took 10.453248739242554s
Amount of data | Check the number of entities for RoLEX took 5.0067901611328125e-05s
Verifiability | Contribs. check for RoLEX took 0.13210225105285645s
Interlinking | sameAs chians check for RoLEX took 0.1341540813446045s
Interlinking | skos check for RoLEX took 0.1492760181427002s
Interlinking | skos check for RoLEX took 0.13637995719909668s
Timeliness | dataset update frequency check for RoLEX took 0.13667011260986328s
Currency | Creation date check for RoLEX took 0.2602989673614502s
Currency | Modification date check for RoLEX took 0.2690281867980957s
Rep.Conc. | URIs length for RoLEX took 53.26635217666626s
Interoperability | New vocabularies check for RoLEX took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for RoLEX took 0.1296541690826416s
Accuracy | Check Functional Property for RoLEX took 0.12955451011657715s
Accuracy | Check Inverse Functional Property for RoLEX took 0.128814697265625s
Accuracy | Check Datatype consistency for RoLEX took 4.048996210098267s
Consistency | Disjoint class check for RoLEX took 0.1315615177154541s
Consistency | Check Misplaced properties for RoLEX took 2.551229953765869s
Consistency | Check Ontology hijacking for RoLEX took 8.24760389328003s
Consistency | Check Invalid usage of undefined classes for RoLEX took 1.7419688701629639s
Consistency | Check Invalid usage of undefined properties for RoLEX took 4.750675678253174s
Conciseness | Check Extensional conciseness for RoLEX took 3.01043438911438s
Security | Sign check for RoLEX took 0.12886500358581543s
Availability | Check URIs Dereferenciability for RoLEX took 7.918470859527588s
Completeness | Calculation of interlinking completeness for RoLEX took 0.3665444850921631s
Reputation | Calculation of the PageRank for RoLEX took 0.021114587783813477s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.3855438232421875e-05s
Interoperability | Check the re-using of existing vocabs for RoLEX took 2.384185791015625e-06s
Believability | Calculation of trust value for RoLEX took 1.2874603271484375e-05s
INFO | --- Analysis for racai-llod-rolex took 173.17615413665771s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 8.702278137207031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.27381134033203125s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.02097320556640625s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0009665489196777344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 9.059906005859375e-06s
INFO | --- Analysis for racai-llod-romanian-treebank took 3.1109015941619873s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 8.726119995117188e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.2652623653411865s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.021026134490966797s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 3.170967102050781e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 1.239776611328125e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 2.725270986557007s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 8.869171142578125e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.26698780059814453s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.0210874080657959s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.000995635986328125s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 4.1484832763671875e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 1.33514404296875e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.617847442626953s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 4.2438507080078125e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.2833735942840576s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.022102832794189453s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 2.956390380859375e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.0013580322265625e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.7537856101989746s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.1333332061767578s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0006899833679199219s
Extra | Recovery of all triples for ROBIN Technical Acquisition Speech Corpus took 9.565634727478027s
Performance | Total latancy measurement for ROBIN Technical Acquisition Speech Corpus took 0.665337324142456s
Amount of data | Number of triples check for ROBIN Technical Acquisition Speech Corpus took 0.30901432037353516s
Interoperability | New terms check for ROBIN Technical Acquisition Speech Corpus took 1.3308966159820557s
Versatility | Languages check for ROBIN Technical Acquisition Speech Corpus took 0.5773544311523438s
Interpretability | Number of blank nodes check for ROBIN Technical Acquisition Speech Corpus took 0.2580416202545166s
Interpretability | RDF structures check for ROBIN Technical Acquisition Speech Corpus took 0.13167452812194824s
Versatility | Serialization formats check for ROBIN Technical Acquisition Speech Corpus took 0.13190174102783203s
Availability | RDF dump link check for ROBIN Technical Acquisition Speech Corpus took 0.14202523231506348s
License | MR license check for ROBIN Technical Acquisition Speech Corpus took 0.13184285163879395s
License | HR license check for ROBIN Technical Acquisition Speech Corpus took 0.13630247116088867s
Amount of data | Number of property check for ROBIN Technical Acquisition Speech Corpus took 0.13427281379699707s
Understandability | Number of label check for ROBIN Technical Acquisition Speech Corpus took 0.1375901699066162s
Understandability | URI regex check for ROBIN Technical Acquisition Speech Corpus took 0.2695765495300293s
Understandability | Vocabs check for ROBIN Technical Acquisition Speech Corpus took 0.13282418251037598s
Verifiability | Authors check for ROBIN Technical Acquisition Speech Corpus took 0.17038822174072266s
Verifiability | Publishers check for ROBIN Technical Acquisition Speech Corpus took 0.13343429565429688s
Performance | Throughput check for ROBIN Technical Acquisition Speech Corpus took 11.621079444885254s
Amount of data | Check the number of entities for ROBIN Technical Acquisition Speech Corpus took 6.723403930664062e-05s
Verifiability | Contribs. check for ROBIN Technical Acquisition Speech Corpus took 0.13052892684936523s
Interlinking | sameAs chians check for ROBIN Technical Acquisition Speech Corpus took 0.1295759677886963s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.1305842399597168s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.13281798362731934s
Timeliness | dataset update frequency check for ROBIN Technical Acquisition Speech Corpus took 0.13358736038208008s
Currency | Creation date check for ROBIN Technical Acquisition Speech Corpus took 0.2633633613586426s
Currency | Modification date check for ROBIN Technical Acquisition Speech Corpus took 0.2833712100982666s
Rep.Conc. | URIs length for ROBIN Technical Acquisition Speech Corpus took 2.469378709793091s
Interoperability | New vocabularies check for ROBIN Technical Acquisition Speech Corpus took 5.9604644775390625e-06s
Consistency | Deprecated classes/propertiers check for ROBIN Technical Acquisition Speech Corpus took 0.13259577751159668s
Accuracy | Check Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.1290454864501953s
Accuracy | Check Inverse Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.13099312782287598s
Accuracy | Check Empty annotation labels for ROBIN Technical Acquisition Speech Corpus took 0.3758673667907715s
Accuracy | Check White space in annotation for ROBIN Technical Acquisition Speech Corpus took 0.009458780288696289s
Accuracy | Check Datatype consistency for ROBIN Technical Acquisition Speech Corpus took 1.2063937187194824s
Consistency | Disjoint class check for ROBIN Technical Acquisition Speech Corpus took 0.12929224967956543s
Consistency | Check Misplaced properties for ROBIN Technical Acquisition Speech Corpus took 0.5003314018249512s
Consistency | Check Ontology hijacking for ROBIN Technical Acquisition Speech Corpus took 2.1657536029815674s
Consistency | Check Invalid usage of undefined classes for ROBIN Technical Acquisition Speech Corpus took 1.1842625141143799s
Consistency | Check Invalid usage of undefined properties for ROBIN Technical Acquisition Speech Corpus took 1.5211434364318848s
Conciseness | Check Extensional conciseness for ROBIN Technical Acquisition Speech Corpus took 0.8298439979553223s
Security | Sign check for ROBIN Technical Acquisition Speech Corpus took 0.13610315322875977s
Availability | Check URIs Dereferenciability for ROBIN Technical Acquisition Speech Corpus took 7.154867172241211s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.2765212059020996s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.02100539207458496s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 3.266334533691406e-05s
Interoperability | Check the re-using of existing vocabs for ROBIN Technical Acquisition Speech Corpus took 2.1457672119140625e-06s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 1.0967254638671875e-05s
INFO | --- Analysis for racai-llod-rtasc took 62.5613739490509s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.1309971809387207s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0005533695220947266s
Extra | Recovery of all triples for SiMoNERo - the Romanian medical treebank took 34.7204110622406s
Performance | Total latancy measurement for SiMoNERo - the Romanian medical treebank took 0.6583187580108643s
Amount of data | Number of triples check for SiMoNERo - the Romanian medical treebank took 1.0731618404388428s
Interoperability | New terms check for SiMoNERo - the Romanian medical treebank took 1.3973536491394043s
Versatility | Languages check for SiMoNERo - the Romanian medical treebank took 2.352386474609375s
Interpretability | Number of blank nodes check for SiMoNERo - the Romanian medical treebank took 0.8699095249176025s
Interpretability | RDF structures check for SiMoNERo - the Romanian medical treebank took 0.13704228401184082s
Versatility | Serialization formats check for SiMoNERo - the Romanian medical treebank took 0.1305246353149414s
Availability | RDF dump link check for SiMoNERo - the Romanian medical treebank took 0.1292707920074463s
License | MR license check for SiMoNERo - the Romanian medical treebank took 0.12995314598083496s
License | HR license check for SiMoNERo - the Romanian medical treebank took 4.513437271118164s
Amount of data | Number of property check for SiMoNERo - the Romanian medical treebank took 0.13335156440734863s
Understandability | Number of label check for SiMoNERo - the Romanian medical treebank took 0.14066290855407715s
Understandability | URI regex check for SiMoNERo - the Romanian medical treebank took 0.2602534294128418s
Understandability | Vocabs check for SiMoNERo - the Romanian medical treebank took 0.13029122352600098s
Verifiability | Authors check for SiMoNERo - the Romanian medical treebank took 0.13039588928222656s
Verifiability | Publishers check for SiMoNERo - the Romanian medical treebank took 0.13040494918823242s
Performance | Throughput check for SiMoNERo - the Romanian medical treebank took 10.699598550796509s
Amount of data | Check the number of entities for SiMoNERo - the Romanian medical treebank took 6.818771362304688e-05s
Verifiability | Contribs. check for SiMoNERo - the Romanian medical treebank took 0.13205385208129883s
Interlinking | sameAs chians check for SiMoNERo - the Romanian medical treebank took 0.1311194896697998s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.1323864459991455s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.13643980026245117s
Timeliness | dataset update frequency check for SiMoNERo - the Romanian medical treebank took 0.13669085502624512s
Currency | Creation date check for SiMoNERo - the Romanian medical treebank took 0.26455163955688477s
Currency | Modification date check for SiMoNERo - the Romanian medical treebank took 0.2648749351501465s
Rep.Conc. | URIs length for SiMoNERo - the Romanian medical treebank took 9.396528244018555s
Interoperability | New vocabularies check for SiMoNERo - the Romanian medical treebank took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for SiMoNERo - the Romanian medical treebank took 0.13088059425354004s
Accuracy | Check Functional Property for SiMoNERo - the Romanian medical treebank took 0.12826943397521973s
Accuracy | Check Inverse Functional Property for SiMoNERo - the Romanian medical treebank took 0.12872838973999023s
Accuracy | Check Empty annotation labels for SiMoNERo - the Romanian medical treebank took 0.6962170600891113s
Accuracy | Check White space in annotation for SiMoNERo - the Romanian medical treebank took 0.018967628479003906s
Accuracy | Check Datatype consistency for SiMoNERo - the Romanian medical treebank took 4.0307793617248535s
Consistency | Disjoint class check for SiMoNERo - the Romanian medical treebank took 0.13538455963134766s
Consistency | Check Misplaced properties for SiMoNERo - the Romanian medical treebank took 1.6815292835235596s
Consistency | Check Ontology hijacking for SiMoNERo - the Romanian medical treebank took 4.4318461418151855s
Consistency | Check Invalid usage of undefined classes for SiMoNERo - the Romanian medical treebank took 1.2108075618743896s
Consistency | Check Invalid usage of undefined properties for SiMoNERo - the Romanian medical treebank took 2.704929828643799s
Conciseness | Check Extensional conciseness for SiMoNERo - the Romanian medical treebank took 2.8855602741241455s
Security | Sign check for SiMoNERo - the Romanian medical treebank took 0.12845301628112793s
Availability | Check URIs Dereferenciability for SiMoNERo - the Romanian medical treebank took 1596.4976704120636s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.4645977020263672s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.02252054214477539s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 6.198883056640625e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 9.822845458984375e-05s
Interoperability | Check the re-using of existing vocabs for SiMoNERo - the Romanian medical treebank took 1.6689300537109375e-06s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 6.9141387939453125e-06s
INFO | --- Analysis for racai-llod-simonero took 1699.051438331604s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.10813713073730469s
Availability | VoID file availability check for Rådata nå! took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.2657344341278076s
Reputation | Calculation of the PageRank for Rådata nå! took 0.022287368774414062s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.344650268554688e-05s
Believability | Calculation of trust value for Rådata nå! took 1.1920928955078125e-05s
INFO | --- Analysis for radatana took 4.099515676498413s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 8.249282836914062e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.27780580520629883s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.020900726318359375s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.981590270996094e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 1.1920928955078125e-05s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 6.959690570831299s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 15.03078842163086s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.28069043159484863s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02064967155456543s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 2.8133392333984375e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.2636184692382812e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 28.855735301971436s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 393.2527267932892s
Availability | VoID file availability check for Polish LGU financial statements took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.27394890785217285s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.021463394165039062s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 3.504753112792969e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 1.0967254638671875e-05s
INFO | --- Analysis for Rb_PL_LGU took 666.1690104007721s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 9.417533874511719e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2677929401397705s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.02104473114013672s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.606910705566406e-05s
Believability | Calculation of trust value for RDF Book Mashup took 1.1205673217773438e-05s
INFO | --- Analysis for rdf-book-mashup took 3.302719831466675s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 8.487701416015625e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.2669651508331299s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020918846130371094s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 9.965896606445312e-05s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 8.821487426757812e-06s
INFO | --- Analysis for rdfize-lastfm took 2.5623223781585693s
Availability | SPARQL endpoint availability check for RDFLicense took 261.42897748947144s
Availability | VoID file availability check for RDFLicense took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.2780184745788574s
Reputation | Calculation of the PageRank for RDFLicense took 0.02080535888671875s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 2.956390380859375e-05s
Believability | Calculation of trust value for RDFLicense took 9.5367431640625e-06s
INFO | --- Analysis for rdflicense took 536.4017949104309s
Availability | SPARQL endpoint availability check for RDFohloh took 9.036064147949219e-05s
Availability | VoID file availability check for RDFohloh took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.2770116329193115s
Reputation | Calculation of the PageRank for RDFohloh took 0.020993709564208984s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 9.107589721679688e-05s
Believability | Calculation of trust value for RDFohloh took 9.775161743164062e-06s
INFO | --- Analysis for rdfohloh took 6.653594017028809s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.5257256031036377s
Availability | VoID file availability check for Reactome RDF took 0.0003943443298339844s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.2857077121734619s
Reputation | Calculation of the PageRank for Reactome RDF took 0.02182626724243164s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.743171691894531e-05s
Believability | Calculation of trust value for Reactome RDF took 9.5367431640625e-06s
INFO | --- Analysis for reactome-rdf took 3.6518588066101074s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.10342717170715332s
Availability | VoID file availability check for Rechtspraak.nl took 0.00040912628173828125s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.27455568313598633s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.131431579589844e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 8.106231689453125e-06s
INFO | --- Analysis for rechtspraak took 2.617858648300171s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 8.392333984375e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.29416584968566895s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.020823955535888672s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.630752563476562e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 9.298324584960938e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 8.13875937461853s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.0545201301574707s
Availability | VoID file availability check for reference.data.gov.uk took 0.0004153251647949219s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.2742435932159424s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020710229873657227s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.0001513957977294922s
Believability | Calculation of trust value for reference.data.gov.uk took 9.5367431640625e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.5753281116485596s
Availability | SPARQL endpoint availability check for RELD took 0.5130009651184082s
Availability | VoID file availability check for RELD took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for RELD took 0.3273591995239258s
Reputation | Calculation of the PageRank for RELD took 0.021106243133544922s
Interlinking | Calculation of Degree of Connection for RELD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for RELD took 2.9802322387695312e-05s
Believability | Calculation of trust value for RELD took 1.0251998901367188e-05s
INFO | --- Analysis for RELD took 3.7674925327301025s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.18201136589050293s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0005574226379394531s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.0979225635528564s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.4252347946166992s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.3738775253295898s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.5066771507263184s
Versatility | Languages check for Repository for Linked Open Archival Data took 18.9994695186615s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 2.036057472229004s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.19194602966308594s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.23091411590576172s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.21784448623657227s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.11131691932678223s
License | MR license check for Repository for Linked Open Archival Data took 0.2673606872558594s
License | HR license check for Repository for Linked Open Archival Data took 7.9503068923950195s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.09483838081359863s
Understandability | Number of label check for Repository for Linked Open Archival Data took 0.8457601070404053s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.28931117057800293s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.10355234146118164s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.11964058876037598s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.12447142601013184s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.399884462356567s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 0.00010657310485839844s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.08327937126159668s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.1100926399230957s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.21529340744018555s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.06257915496826172s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.23743319511413574s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.28619813919067383s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.1835329532623291s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.615373373031616s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.08602428436279297s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.09565043449401855s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.0817725658416748s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.30449843406677246s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.027760028839111328s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.03132939338684082s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.13714194297790527s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 1.9855639934539795s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.19430804252624512s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.442479133605957s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.1140658855438232s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.1231675148010254s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.037964820861816406s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.11457443237304688s
Security | Sign check for Repository for Linked Open Archival Data took 0.34360599517822266s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 834.8637096881866s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.41770100593566895s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.02118062973022461s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 4.100799560546875e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 1.1920928955078125e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 1.2636184692382812e-05s
INFO | --- Analysis for reload took 950.972490310669s
Availability | SPARQL endpoint availability check for Land use merced dataset took 8.320808410644531e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.27231812477111816s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.02115321159362793s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.0994415283203125e-05s
Believability | Calculation of trust value for Land use merced dataset took 1.239776611328125e-05s
INFO | --- Analysis for remote_Sensing took 3.2320756912231445s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 10.78851866722107s
Availability | VoID file availability check for Renewable Energy Generators took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.3264327049255371s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.02181720733642578s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.315376281738281e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 8.58306884765625e-06s
INFO | --- Analysis for renewable_energy_generators took 131.45910453796387s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.03889012336730957s
Availability | VoID file availability check for research.data.gov.uk took 0.00040435791015625s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.2643864154815674s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020905733108520508s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.083747863769531e-05s
Believability | Calculation of trust value for research.data.gov.uk took 1.0013580322265625e-05s
INFO | --- Analysis for research-data-gov-uk took 2.5286026000976562s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.2438507080078125e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.2760286331176758s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.413459777832031e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 9.775161743164062e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 3.9336163997650146s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.13154387474060059s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.28041815757751465s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.3855438232421875e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 1.0251998901367188e-05s
INFO | --- Analysis for revistas_turismo took 2.6090080738067627s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.2645866870880127s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.2667570114135742s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.022165536880493164s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011801719665527344s
Believability | Calculation of trust value for Revyu.com - Review Anything took 1.2874603271484375e-05s
INFO | --- Analysis for revyu took 2.725421905517578s
Availability | SPARQL endpoint availability check for sdafsadf took 0.30506110191345215s
Availability | VoID file availability check for sdafsadf took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.26462674140930176s
Reputation | Calculation of the PageRank for sdafsadf took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.0040740966796875e-05s
Believability | Calculation of trust value for sdafsadf took 5.7220458984375e-06s
INFO | --- Analysis for rgsdfg took 3.1914875507354736s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 8.559226989746094e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.2852203845977783s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.020805835723876953s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.7206878662109375e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 1.1682510375976562e-05s
INFO | --- Analysis for riese took 22.515950679779053s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.22149372100830078s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0005500316619873047s
Extra | Recovery of all triples for Répertoire International des Sources Musicales - RISM took 22.53769063949585s
Performance | Total latancy measurement for Répertoire International des Sources Musicales - RISM took 0.47678351402282715s
Amount of data | Number of triples check for Répertoire International des Sources Musicales - RISM took 54.87435841560364s
Interoperability | New terms check for Répertoire International des Sources Musicales - RISM took 1.9333112239837646s
Versatility | Languages check for Répertoire International des Sources Musicales - RISM took 156.4104471206665s
Interpretability | Number of blank nodes check for Répertoire International des Sources Musicales - RISM took 49.40709710121155s
Security | Check HTTPS for Répertoire International des Sources Musicales - RISM took 0.20912694931030273s
Interpretability | RDF structures check for Répertoire International des Sources Musicales - RISM took 0.18660545349121094s
Versatility | Serialization formats check for Répertoire International des Sources Musicales - RISM took 0.13503313064575195s
Availability | RDF dump link check for Répertoire International des Sources Musicales - RISM took 0.08910131454467773s
License | MR license check for Répertoire International des Sources Musicales - RISM took 0.11835813522338867s
License | HR license check for Répertoire International des Sources Musicales - RISM took 300.1008040904999s
Amount of data | Number of property check for Répertoire International des Sources Musicales - RISM took 0.13250303268432617s
Understandability | Number of label check for Répertoire International des Sources Musicales - RISM took 8.724893808364868s
Understandability | URI regex check for Répertoire International des Sources Musicales - RISM took 0.20524954795837402s
Understandability | Vocabs check for Répertoire International des Sources Musicales - RISM took 0.09914302825927734s
Verifiability | Authors check for Répertoire International des Sources Musicales - RISM took 0.08309650421142578s
Verifiability | Publishers check for Répertoire International des Sources Musicales - RISM took 0.08373785018920898s
Performance | Throughput check for Répertoire International des Sources Musicales - RISM took 10.294994831085205s
Amount of data | Check the number of entities for Répertoire International des Sources Musicales - RISM took 7.653236389160156e-05s
Verifiability | Contribs. check for Répertoire International des Sources Musicales - RISM took 0.08336138725280762s
Interlinking | sameAs chians check for Répertoire International des Sources Musicales - RISM took 1.5995044708251953s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.12946796417236328s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.1149437427520752s
Timeliness | dataset update frequency check for Répertoire International des Sources Musicales - RISM took 0.08322763442993164s
Currency | Creation date check for Répertoire International des Sources Musicales - RISM took 0.22708892822265625s
Currency | Modification date check for Répertoire International des Sources Musicales - RISM took 0.23062801361083984s
Rep.Conc. | URIs length for Répertoire International des Sources Musicales - RISM took 77.92185950279236s
Interoperability | New vocabularies check for Répertoire International des Sources Musicales - RISM took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Répertoire International des Sources Musicales - RISM took 0.11551809310913086s
Accuracy | Check Functional Property for Répertoire International des Sources Musicales - RISM took 0.11206603050231934s
Accuracy | Check Inverse Functional Property for Répertoire International des Sources Musicales - RISM took 0.08851361274719238s
Accuracy | Check Empty annotation labels for Répertoire International des Sources Musicales - RISM took 16.62988567352295s
Accuracy | Check White space in annotation for Répertoire International des Sources Musicales - RISM took 2.368453025817871s
Accuracy | Check Datatype consistency for Répertoire International des Sources Musicales - RISM took 3.727792501449585s
Consistency | Disjoint class check for Répertoire International des Sources Musicales - RISM took 0.09831929206848145s
Consistency | Check Misplaced properties for Répertoire International des Sources Musicales - RISM took 48.470901012420654s
Consistency | Check Ontology hijacking for Répertoire International des Sources Musicales - RISM took 5.0923707485198975s
Consistency | Check Invalid usage of undefined classes for Répertoire International des Sources Musicales - RISM took 1.3196239471435547s
Consistency | Check Invalid usage of undefined properties for Répertoire International des Sources Musicales - RISM took 48.741596937179565s
Conciseness | Check Extensional conciseness for Répertoire International des Sources Musicales - RISM took 2.700416326522827s
Security | Sign check for Répertoire International des Sources Musicales - RISM took 0.09815645217895508s
Availability | Check URIs Dereferenciability for Répertoire International des Sources Musicales - RISM took 3.049370050430298s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.4026355743408203s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.021842002868652344s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 5.3882598876953125e-05s
Interoperability | Check the re-using of existing vocabs for Répertoire International des Sources Musicales - RISM took 2.6226043701171875e-06s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 1.0013580322265625e-05s
INFO | --- Analysis for rism took 1239.9142708778381s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.08247828483581543s
Availability | VoID file availability check for RISM Authority data took 0.0006163120269775391s
Extra | Recovery of all triples for RISM Authority data took 22.83484983444214s
Performance | Total latancy measurement for RISM Authority data took 0.4451937675476074s
Amount of data | Number of triples check for RISM Authority data took 52.23183584213257s
Interoperability | New terms check for RISM Authority data took 1.5541696548461914s
Versatility | Languages check for RISM Authority data took 157.34934496879578s
Interpretability | Number of blank nodes check for RISM Authority data took 49.253981828689575s
Security | Check HTTPS for RISM Authority data took 0.13757014274597168s
Interpretability | RDF structures check for RISM Authority data took 0.10844063758850098s
Versatility | Serialization formats check for RISM Authority data took 0.12387275695800781s
Availability | RDF dump link check for RISM Authority data took 0.09495306015014648s
License | MR license check for RISM Authority data took 0.10844874382019043s
License | HR license check for RISM Authority data took 300.0886721611023s
Amount of data | Number of property check for RISM Authority data took 0.12129759788513184s
Understandability | Number of label check for RISM Authority data took 3.662330150604248s
Understandability | URI regex check for RISM Authority data took 0.2125415802001953s
Understandability | Vocabs check for RISM Authority data took 0.09638404846191406s
Verifiability | Authors check for RISM Authority data took 0.08482122421264648s
Verifiability | Publishers check for RISM Authority data took 0.09470033645629883s
Performance | Throughput check for RISM Authority data took 10.530714988708496s
Amount of data | Check the number of entities for RISM Authority data took 7.486343383789062e-05s
Verifiability | Contribs. check for RISM Authority data took 0.0996863842010498s
Interlinking | sameAs chians check for RISM Authority data took 1.468339204788208s
Interlinking | skos check for RISM Authority data took 0.11766672134399414s
Interlinking | skos check for RISM Authority data took 0.09497976303100586s
Timeliness | dataset update frequency check for RISM Authority data took 0.09850573539733887s
Currency | Creation date check for RISM Authority data took 0.21615862846374512s
Currency | Modification date check for RISM Authority data took 0.2316451072692871s
Rep.Conc. | URIs length for RISM Authority data took 76.62658357620239s
Interoperability | New vocabularies check for RISM Authority data took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for RISM Authority data took 0.1353321075439453s
Accuracy | Check Functional Property for RISM Authority data took 0.11271834373474121s
Accuracy | Check Inverse Functional Property for RISM Authority data took 0.10746550559997559s
Accuracy | Check Empty annotation labels for RISM Authority data took 10.880693197250366s
Accuracy | Check White space in annotation for RISM Authority data took 2.375812292098999s
Accuracy | Check Datatype consistency for RISM Authority data took 3.8553433418273926s
Consistency | Disjoint class check for RISM Authority data took 0.09552335739135742s
Consistency | Check Misplaced properties for RISM Authority data took 48.31969356536865s
Consistency | Check Ontology hijacking for RISM Authority data took 5.133377552032471s
Consistency | Check Invalid usage of undefined classes for RISM Authority data took 1.3477323055267334s
Consistency | Check Invalid usage of undefined properties for RISM Authority data took 49.5593364238739s
Conciseness | Check Extensional conciseness for RISM Authority data took 2.798611879348755s
Security | Sign check for RISM Authority data took 0.09673547744750977s
Availability | Check URIs Dereferenciability for RISM Authority data took 1.9596061706542969s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.686194896697998s
Reputation | Calculation of the PageRank for RISM Authority data took 0.02116870880126953s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 5.817413330078125e-05s
Interoperability | Check the re-using of existing vocabs for RISM Authority data took 1.6689300537109375e-06s
Believability | Calculation of trust value for RISM Authority data took 1.1682510375976562e-05s
INFO | --- Analysis for rism-authorities took 1226.300282239914s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 0.00010585784912109375s
Availability | VoID file availability check for engineering equipment ontology took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.2726619243621826s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 2.9802322387695312e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.2159347534179688e-05s
INFO | --- Analysis for rk took 2.4868111610412598s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.05446624755859375s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.2719461917877197s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.021472454071044922s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0008103847503662109s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002827644348144531s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.6338114738464355s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.027525901794433594s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.26503682136535645s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.02153635025024414s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00013947486877441406s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-budapest took 2.524637222290039s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.030546903610229492s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.26909899711608887s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.02125406265258789s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00020551681518554688s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-citeseer took 2.5334062576293945s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.027225494384765625s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0003273487091064453s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.2631802558898926s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0236051082611084s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0001552104949951172s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-cordis took 2.5104992389678955s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.039652109146118164s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.26676225662231445s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.022563695907592773s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.0001571178436279297s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-courseware took 2.582794666290283s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.03541231155395508s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.29560351371765137s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.021198749542236328s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.0728836059570312e-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 4.220008850097656e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.556666851043701s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0465390682220459s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.2725214958190918s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.022667646408081055s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00012087821960449219s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-curriculum took 2.5495171546936035s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.029522418975830078s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.30196380615234375s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.0211029052734375s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.2928924560546875e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.5617308616638184s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.02785205841064453s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0004220008850097656s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.26879286766052246s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002357959747314453s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-dblp took 2.5601606369018555s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.03353071212768555s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.27375125885009766s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.02111530303955078s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 8.249282836914062e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-deepblue took 2.59535551071167s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.3343029022216797s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.2716376781463623s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.021022558212280273s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.822845458984375e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-deploy took 3.612988233566284s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.027195453643798828s
Availability | VoID file availability check for digitaleconomy took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.26112794876098633s
Reputation | Calculation of the PageRank for digitaleconomy took 0.02085733413696289s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 2.9802322387695312e-05s
Believability | Calculation of trust value for digitaleconomy took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.470935106277466s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.0285341739654541s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2612190246582031s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.02106499671936035s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.000148773193359375s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-dotac took 2.5385167598724365s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.028388500213623047s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00041747093200683594s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2799081802368164s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02129387855529785s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.458427429199219e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-ecs took 3.9005346298217773s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.06060218811035156s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0004050731658935547s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.2593517303466797s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0001811981201171875s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-eprints took 2.5292580127716064s
Availability | SPARQL endpoint availability check for epsrc took 0.04438924789428711s
Availability | VoID file availability check for epsrc took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for epsrc took 0.2685091495513916s
Reputation | Calculation of the PageRank for epsrc took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for epsrc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.7220458984375e-05s
Believability | Calculation of trust value for epsrc took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-epsrc took 2.5646543502807617s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.03430938720703125s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.27634739875793457s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.02053356170654297s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 7.82012939453125e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-era took 2.5290021896362305s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.03553485870361328s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.27356863021850586s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.021860122680664062s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010228157043457031s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-eurecom took 2.542073965072632s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.40110230445861816s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.2669639587402344s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020587921142578125s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 8.7738037109375e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-ft took 3.864561080932617s
Availability | SPARQL endpoint availability check for fun took 0.028820514678955078s
Availability | VoID file availability check for fun took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for fun took 0.2790520191192627s
Reputation | Calculation of the PageRank for fun took 0.02086353302001953s
Interlinking | Calculation of Degree of Connection for fun took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for fun took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for fun took 6.866455078125e-05s
Believability | Calculation of trust value for fun took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.5047504901885986s
Availability | SPARQL endpoint availability check for gdlc took 0.034348249435424805s
Availability | VoID file availability check for gdlc took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for gdlc took 0.2739725112915039s
Reputation | Calculation of the PageRank for gdlc took 0.021112680435180664s
Interlinking | Calculation of Degree of Connection for gdlc took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.794929504394531e-05s
Believability | Calculation of trust value for gdlc took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-gdlc took 2.4939777851104736s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.03513455390930176s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.00039267539978027344s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.27384138107299805s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.02100205421447754s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011515617370605469s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-ibm took 2.526824474334717s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.03497600555419922s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00035834312438964844s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.26370882987976074s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020654916763305664s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001327991485595703s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.5040011405944824s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.03604435920715332s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0004172325134277344s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.27649784088134766s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.020934343338012695s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00014972686767578125s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-irit took 2.5112431049346924s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.03483843803405762s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0003814697265625s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.27263832092285156s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.022045373916625977s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 7.152557373046875e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-italy took 2.5038905143737793s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.03724241256713867s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.27552366256713867s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.02143692970275879s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.176399230957031e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-jisc took 2.5441055297851562s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0711669921875s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.2740437984466553s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.020975828170776367s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.267692565917969e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-kaunas took 2.672847032546997s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.04268336296081543s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.27900028228759766s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.022041797637939453s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0010514259338378906s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0002028942108154297s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-kisti took 2.5974833965301514s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.05185055732727051s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.2711598873138428s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.021205902099609375s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0009014606475830078s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00017571449279785156s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-laas took 2.5877768993377686s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.035352230072021484s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.2694075107574463s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.020638465881347656s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.151199340820312e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 2.5615973472595215s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.028044462203979492s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.26770591735839844s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.0001926422119140625s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-newcastle took 2.5323410034179688s
Availability | SPARQL endpoint availability check for notube took 0.033850669860839844s
Availability | VoID file availability check for notube took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for notube took 0.2751469612121582s
Reputation | Calculation of the PageRank for notube took 0.020835161209106445s
Interlinking | Calculation of Degree of Connection for notube took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for notube took 0.0008924007415771484s
Interlinking | Calculation of Clustering coefficient for notube took 4.9114227294921875e-05s
Believability | Calculation of trust value for notube took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-notube took 2.5277509689331055s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.04001903533935547s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.2733430862426758s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.02213430404663086s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00012969970703125s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-nsf took 2.561751365661621s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.028542041778564453s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.2722039222717285s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.02039623260498047s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00015234947204589844s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-oai took 2.4998300075531006s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.033075809478759766s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.281848669052124s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.02169966697692871s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.462501525878906e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-os took 2.5671966075897217s
Availability | SPARQL endpoint availability check for photos took 0.03350663185119629s
Availability | VoID file availability check for photos took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for photos took 0.2672388553619385s
Reputation | Calculation of the PageRank for photos took 0.020640850067138672s
Interlinking | Calculation of Degree of Connection for photos took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for photos took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for photos took 7.677078247070312e-05s
Believability | Calculation of trust value for photos took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-photos took 2.531090021133423s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.02775120735168457s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.292309045791626s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.021062850952148438s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011467933654785156s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-pisa took 2.523719549179077s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.02917027473449707s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.2680637836456299s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.022042036056518555s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019693374633789062s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.5508830547332764s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0336766242980957s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.2652432918548584s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0001506805419921875s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-resex took 2.5399227142333984s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.030742168426513672s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0010535717010498047s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.2768239974975586s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020732641220092773s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.5367431640625e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-risks took 2.5105819702148438s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.03799319267272949s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00041985511779785156s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.2731149196624756s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020795345306396484s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012445449829101562s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.5591373443603516s
Availability | SPARQL endpoint availability check for roni took 0.027765989303588867s
Availability | VoID file availability check for roni took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for roni took 0.27094244956970215s
Reputation | Calculation of the PageRank for roni took 0.02298426628112793s
Interlinking | Calculation of Degree of Connection for roni took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for roni took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for roni took 3.361701965332031e-05s
Believability | Calculation of trust value for roni took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-roni took 2.5073585510253906s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.03566861152648926s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.2627067565917969s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.02055811882019043s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.000217437744140625s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-southampton took 2.4981775283813477s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.0279996395111084s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.2668642997741699s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.02173018455505371s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00011157989501953125s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-ulm took 2.620222330093384s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.04464602470397949s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.00037360191345214844s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.28435850143432617s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.02073502540588379s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 0.0001049041748046875s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-unlocode took 2.553013324737549s
Availability | SPARQL endpoint availability check for webconf took 0.02796316146850586s
Availability | VoID file availability check for webconf took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for webconf took 0.26361751556396484s
Reputation | Calculation of the PageRank for webconf took 0.022753000259399414s
Interlinking | Calculation of Degree of Connection for webconf took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for webconf took 9.846687316894531e-05s
Believability | Calculation of trust value for webconf took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-webconf took 13.007299661636353s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.02681589126586914s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0004208087921142578s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.27181386947631836s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.022147655487060547s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 6.842613220214844e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-webscience took 2.492644786834717s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.03979039192199707s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.263887882232666s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.021048307418823242s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.0002048015594482422s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-wiki took 2.5814530849456787s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.03512930870056152s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.2729063034057617s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.02300429344177246s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.918212890625e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-wordnet took 2.505206346511841s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.423825740814209s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0005338191986083984s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 55.759169816970825s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.42934608459472656s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 1.4614317417144775s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.5810842514038086s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 4.626745939254761s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.261937141418457s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.08264517784118652s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.08124589920043945s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.07742810249328613s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.07879257202148438s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.08036136627197266s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.07787466049194336s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.136444091796875s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.15867161750793457s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.07943010330200195s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.07929348945617676s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.07883954048156738s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.238694667816162s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 8.225440979003906e-05s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.08681988716125488s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.0908956527709961s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.08233475685119629s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.08174610137939453s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.09658694267272949s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.15758776664733887s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.1604304313659668s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 18.02265477180481s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.08221292495727539s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.07861137390136719s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.07695555686950684s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 3.82246470451355s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.08061718940734863s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 2.824084997177124s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 6.565439939498901s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.4340944290161133s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.053687334060669s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 2.973088264465332s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.0789639949798584s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 480.86697030067444s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.34630322456359863s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.02285480499267578s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0010006427764892578s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 0.0001049041748046875s
Interoperability | Check the re-using of existing vocabs for ROCEEH Out of Africa Database (ROAD) took 1.9073486328125e-06s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 1.2874603271484375e-05s
INFO | --- Analysis for roceeh-road took 617.3364851474762s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 4.076957702636719e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.2797417640686035s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.021535158157348633s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 2.86102294921875e-05s
Believability | Calculation of trust value for ontology terrorist attack took 1.0013580322265625e-05s
INFO | --- Analysis for ROSHANI took 4.351445913314819s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.1484832763671875e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.2718079090118408s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.020519495010375977s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.170967102050781e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 1.0967254638671875e-05s
INFO | --- Analysis for ROSHANI_SAHU took 2.4742085933685303s
Availability | SPARQL endpoint availability check for x took 5.173683166503906e-05s
Availability | VoID file availability check for x took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for x took 0.2648501396179199s
Reputation | Calculation of the PageRank for x took 0.02260303497314453s
Interlinking | Calculation of Degree of Connection for x took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for x took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for x took 2.9325485229492188e-05s
Believability | Calculation of trust value for x took 6.198883056640625e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.4298834800720215s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 8.535385131835938e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.27587032318115234s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.021962404251098633s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0011343955993652344s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 8.654594421386719e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 7.3909759521484375e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 3.846834659576416s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 8.7738037109375e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.2622365951538086s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020954132080078125s
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.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.176399230957031e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 1.1920928955078125e-05s
INFO | --- Analysis for rubentaelman took 3.0760083198547363s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 8.606910705566406e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.2654719352722168s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.02191948890686035s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.249282836914062e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 9.298324584960938e-06s
INFO | --- Analysis for rubenverborgh took 3.9512903690338135s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 392.60888385772705s
Availability | VoID file availability check for Russian Universities Specialities took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.2634773254394531s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.02150726318359375s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.601478576660156e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 1.0251998901367188e-05s
INFO | --- Analysis for russian-universities-specialities took 667.5741846561432s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 3.696439504623413s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.2746927738189697s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.021128177642822266s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.0040740966796875e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 1.239776611328125e-05s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 8.502254009246826s
Availability | SPARQL endpoint availability check for SALDO-RDF took 0.9203801155090332s
Availability | VoID file availability check for SALDO-RDF took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.29440927505493164s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.02130722999572754s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 4.315376281738281e-05s
Believability | Calculation of trust value for SALDO-RDF took 1.1682510375976562e-05s
INFO | --- Analysis for saldo-rdf took 5.454682350158691s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.613147497177124s
Availability | VoID file availability check for SALDOM-RDF took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.2633330821990967s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.021825790405273438s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.552436828613281e-05s
Believability | Calculation of trust value for SALDOM-RDF took 1.049041748046875e-05s
INFO | --- Analysis for saldom-rdf took 4.691322088241577s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 8.225440979003906e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.2746243476867676s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.021117448806762695s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010466575622558594s
Believability | Calculation of trust value for Salzburgerland DE took 1.4781951904296875e-05s
INFO | --- Analysis for salzburgerland-com-de took 3.120556116104126s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 8.344650268554688e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.27477478981018066s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.020996570587158203s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00010251998901367188s
Believability | Calculation of trust value for Salzburgerland EN took 1.239776611328125e-05s
INFO | --- Analysis for salzburgerland-com-en took 2.920605182647705s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 9.34600830078125e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.286405086517334s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.020778894424438477s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00011014938354492188s
Believability | Calculation of trust value for Salzburgerland IT took 1.3113021850585938e-05s
INFO | --- Analysis for salzburgerland-com-it took 3.0207223892211914s
Availability | SPARQL endpoint availability check for sandrart.net took 4.1961669921875e-05s
Availability | VoID file availability check for sandrart.net took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.26511597633361816s
Reputation | Calculation of the PageRank for sandrart.net took 0.020893335342407227s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.699562072753906e-05s
Believability | Calculation of trust value for sandrart.net took 1.2874603271484375e-05s
INFO | --- Analysis for sandrart-net took 3.5609776973724365s
Availability | SPARQL endpoint availability check for Taxons  took 0.1772475242614746s
Availability | VoID file availability check for Taxons  took 0.0004706382751464844s
Extra | Recovery of all triples for Taxons  took 20.06665015220642s
Performance | Total latancy measurement for Taxons  took 0.40103769302368164s
Amount of data | Number of triples check for Taxons  took 1.9997389316558838s
Interoperability | New terms check for Taxons  took 1.799546480178833s
Versatility | Languages check for Taxons  took 36.25165271759033s
Interpretability | Number of blank nodes check for Taxons  took 0.8215055465698242s
Security | Check HTTPS for Taxons  took 0.17079854011535645s
Interpretability | RDF structures check for Taxons  took 1.0288684368133545s
Versatility | Serialization formats check for Taxons  took 0.4414539337158203s
Availability | RDF dump link check for Taxons  took 0.22458839416503906s
License | MR license check for Taxons  took 1.5554251670837402s
License | HR license check for Taxons  took 1.8978824615478516s
Amount of data | Number of property check for Taxons  took 0.11947274208068848s
Understandability | Number of label check for Taxons  took 2.9370181560516357s
Understandability | URI regex check for Taxons  took 0.46198153495788574s
Understandability | Vocabs check for Taxons  took 0.17983365058898926s
Verifiability | Authors check for Taxons  took 0.11794543266296387s
Verifiability | Publishers check for Taxons  took 0.08081746101379395s
Performance | Throughput check for Taxons  took 10.382999658584595s
Amount of data | Check the number of entities for Taxons  took 6.818771362304688e-05s
Verifiability | Contribs. check for Taxons  took 0.07319092750549316s
Interlinking | sameAs chians check for Taxons  took 0.2517073154449463s
Interlinking | skos check for Taxons  took 0.13625526428222656s
Interlinking | skos check for Taxons  took 0.07755613327026367s
Timeliness | dataset update frequency check for Taxons  took 0.3732156753540039s
Currency | Creation date check for Taxons  took 0.1914355754852295s
Currency | Modification date check for Taxons  took 0.21335530281066895s
Rep.Conc. | URIs length for Taxons  took 8.27839732170105s
Interoperability | New vocabularies check for Taxons  took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.09694552421569824s
Accuracy | Check Functional Property for Taxons  took 0.325486421585083s
Accuracy | Check Inverse Functional Property for Taxons  took 0.18529510498046875s
Accuracy | Check Empty annotation labels for Taxons  took 4.163703918457031s
Accuracy | Check White space in annotation for Taxons  took 0.2971177101135254s
Accuracy | Check Datatype consistency for Taxons  took 0.2646777629852295s
Consistency | Disjoint class check for Taxons  took 0.10426998138427734s
Consistency | Check Misplaced properties for Taxons  took 3.7210538387298584s
Consistency | Misplaced classes for Taxons  took 0.9417402744293213s
Consistency | Check Ontology hijacking for Taxons  took 4.205496549606323s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.308716058731079s
Consistency | Check Invalid usage of undefined properties for Taxons  took 5.0032312870025635s
Conciseness | Check Extensional conciseness for Taxons  took 0.2845895290374756s
Conciseness | Check Intensional conciseness for Taxons  took 0.17550158500671387s
Security | Sign check for Taxons  took 0.7637467384338379s
Availability | Check URIs Dereferenciability for Taxons  took 1556.4226274490356s
Completeness | Calculation of interlinking completeness for Taxons  took 0.4653773307800293s
Reputation | Calculation of the PageRank for Taxons  took 0.021799564361572266s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Taxons  took 7.700920104980469e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 2.384185791015625e-06s
Believability | Calculation of trust value for Taxons  took 1.049041748046875e-05s
INFO | --- Analysis for sandre took 1735.408864736557s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 69.73742914199829s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.2973673343658447s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.02088332176208496s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.743171691894531e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 1.1444091796875e-05s
INFO | --- Analysis for sanskrit-english-lexicon took 181.95079922676086s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 269.0959219932556s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0007641315460205078s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.307361364364624s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 3.361701965332031e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 1.0967254638671875e-05s
INFO | --- Analysis for santillana_guide_dataset took 673.308516740799s
Availability | SPARQL endpoint availability check for SATAR test  took 8.7738037109375e-05s
Availability | VoID file availability check for SATAR test  took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.30987119674682617s
Reputation | Calculation of the PageRank for SATAR test  took 0.020564794540405273s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 2.8371810913085938e-05s
Believability | Calculation of trust value for SATAR test  took 1.1205673217773438e-05s
INFO | --- Analysis for SATAR_test took 4.470006227493286s
Availability | SPARQL endpoint availability check for SCBG Data took 21.547245502471924s
Availability | VoID file availability check for SCBG Data took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.278778076171875s
Reputation | Calculation of the PageRank for SCBG Data took 0.020829200744628906s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 7.772445678710938e-05s
Believability | Calculation of trust value for SCBG Data took 1.1444091796875e-05s
INFO | --- Analysis for SCBG-Data took 54.2294762134552s
Availability | SPARQL endpoint availability check for Schemantra took 8.58306884765625e-05s
Availability | VoID file availability check for Schemantra took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Schemantra took 0.2711806297302246s
Reputation | Calculation of the PageRank for Schemantra took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Schemantra took 2.956390380859375e-05s
Believability | Calculation of trust value for Schemantra took 1.1682510375976562e-05s
INFO | --- Analysis for Schemantra took 2.4444398880004883s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 2.052568197250366s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.2754666805267334s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.02113652229309082s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0006871223449707031s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.4332275390625e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 1.2636184692382812e-05s
INFO | --- Analysis for schemapedia took 4.890504598617554s
Availability | SPARQL endpoint availability check for Scholarometer took 4.291534423828125e-05s
Availability | VoID file availability check for Scholarometer took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.28353309631347656s
Reputation | Calculation of the PageRank for Scholarometer took 0.020938873291015625s
Interlinking | Calculation of Degree of Connection for Scholarometer took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Scholarometer took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.106231689453125e-05s
Believability | Calculation of trust value for Scholarometer took 1.3113021850585938e-05s
INFO | --- Analysis for scholarometer took 6.996716737747192s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 8.845329284667969e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.2620046138763428s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.02075958251953125s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 2.9087066650390625e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 9.059906005859375e-06s
INFO | --- Analysis for scoreboard took 4.536506652832031s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 8.487701416015625e-05s
Availability | VoID file availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.27306294441223145s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.02147078514099121s
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.2636184692382812e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.314018249511719e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 1.1682510375976562e-05s
INFO | --- Analysis for SDDEC took 27.274208068847656s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 8.630752563476562e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.000392913818359375s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.2768394947052002s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.022937536239624023s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 3.0517578125e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.239776611328125e-05s
INFO | --- Analysis for SDG took 3.3566291332244873s
Availability | SPARQL endpoint availability check for sears.com took 9.036064147949219e-05s
Availability | VoID file availability check for sears.com took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for sears.com took 0.28114938735961914s
Reputation | Calculation of the PageRank for sears.com took 0.020717859268188477s
Interlinking | Calculation of Degree of Connection for sears.com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sears.com took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for sears.com took 7.152557373046875e-05s
Believability | Calculation of trust value for sears.com took 1.1682510375976562e-05s
INFO | --- Analysis for sears took 5.198624610900879s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.054361820220947266s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.2678494453430176s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020580530166625977s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.130073547363281e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.5367431640625e-06s
INFO | --- Analysis for sec-rdfabout took 6.285207986831665s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.633483409881592s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.30252695083618164s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.020824432373046875s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 9.512901306152344e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for secold took 167.77895736694336s
Availability | SPARQL endpoint availability check for semanlink took 8.535385131835938e-05s
Availability | VoID file availability check for semanlink took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for semanlink took 0.27132749557495117s
Reputation | Calculation of the PageRank for semanlink took 0.021493196487426758s
Interlinking | Calculation of Degree of Connection for semanlink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.0001480579376220703s
Believability | Calculation of trust value for semanlink took 1.0251998901367188e-05s
INFO | --- Analysis for semanlink took 3.7480387687683105s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.06469297409057617s
Availability | VoID file availability check for Semantic Universe Data took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.25647854804992676s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.021238327026367188s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.2901763916015625e-05s
Believability | Calculation of trust value for Semantic Universe Data took 5.7220458984375e-06s
INFO | --- Analysis for semantic-universe took 2.518514394760132s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.477411031723022s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.2738509178161621s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011205673217773438s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.0251998901367188e-05s
INFO | --- Analysis for semantic-web-dog-food took 83.20778322219849s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 8.463859558105469e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.26152753829956055s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020771503448486328s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.38690185546875e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 1.0728836059570312e-05s
INFO | --- Analysis for semantic-web-grundlagen took 3.128774404525757s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.1961669921875e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.26680445671081543s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.021574974060058594s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.130073547363281e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 8.106231689453125e-06s
INFO | --- Analysis for semantic-xbrl took 3.331362724304199s
Availability | SPARQL endpoint availability check for Semantic Quran took 4.047471046447754s
Availability | VoID file availability check for Semantic Quran took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Semantic Quran took 0.2739095687866211s
Reputation | Calculation of the PageRank for Semantic Quran took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Semantic Quran took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic Quran took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Semantic Quran took 6.628036499023438e-05s
Believability | Calculation of trust value for Semantic Quran took 1.049041748046875e-05s
INFO | --- Analysis for semanticquran took 13.222057819366455s
Availability | SPARQL endpoint availability check for SemanticTweet took 8.559226989746094e-05s
Availability | VoID file availability check for SemanticTweet took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.27735161781311035s
Reputation | Calculation of the PageRank for SemanticTweet took 0.02135014533996582s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.888938903808594e-05s
Believability | Calculation of trust value for SemanticTweet took 9.5367431640625e-06s
INFO | --- Analysis for semantictweet took 2.5903589725494385s
Availability | SPARQL endpoint availability check for semanticweb.org took 8.702278137207031e-05s
Availability | VoID file availability check for semanticweb.org took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.27100133895874023s
Reputation | Calculation of the PageRank for semanticweb.org took 0.021889686584472656s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 8.296966552734375e-05s
Believability | Calculation of trust value for semanticweb.org took 1.0728836059570312e-05s
INFO | --- Analysis for semanticweb-org took 22.70640516281128s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.0744481086730957s
Availability | VoID file availability check for Semantic CrunchBase took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.2679147720336914s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.02104926109313965s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.794929504394531e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 1.239776611328125e-05s
INFO | --- Analysis for semsol-crunchbase took 2.5813395977020264s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.2615516185760498s
Availability | VoID file availability check for SentimentWortschatz took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.2776041030883789s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020496606826782227s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.00543212890625e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.2636184692382812e-05s
INFO | --- Analysis for sentiws took 4.031543970108032s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.018468856811523s
Availability | VoID file availability check for seoul-bike-data took 0.0007483959197998047s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.27179455757141113s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.021186351776123047s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0010013580322265625s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 4.410743713378906e-05s
Believability | Calculation of trust value for seoul-bike-data took 1.2636184692382812e-05s
INFO | --- Analysis for seoul-bike-data took 72.75722694396973s
Availability | SPARQL endpoint availability check for Serendipity took 8.140660762786865s
Availability | VoID file availability check for Serendipity took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Serendipity took 0.28194475173950195s
Reputation | Calculation of the PageRank for Serendipity took 0.022300004959106445s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Serendipity took 7.009506225585938e-05s
Believability | Calculation of trust value for Serendipity took 1.0251998901367188e-05s
INFO | --- Analysis for serendipity took 15.796274423599243s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 8.797645568847656e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.26967859268188477s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.020833730697631836s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.0279159545898438e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 1.0728836059570312e-05s
INFO | --- Analysis for Sherry_Wine took 2.5944955348968506s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.076957702636719e-05s
Availability | VoID file availability check for Sherry Wine took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.26877403259277344s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020748138427734375s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.0040740966796875e-05s
Believability | Calculation of trust value for Sherry Wine took 1.2159347534179688e-05s
INFO | --- Analysis for Sherry_Wine_ took 2.637669801712036s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.18055295944213867s
Availability | VoID file availability check for Shoah victims? names took 0.19473004341125488s
Extra | Recovery of all triples for Shoah victims? names took 1.0322821140289307s
Performance | Total latancy measurement for Shoah victims? names took 0.333263635635376s
Amount of data | Number of triples check for Shoah victims? names took 1.6685090065002441s
Interoperability | New terms check for Shoah victims? names took 1.7322969436645508s
Versatility | Languages check for Shoah victims? names took 18.679922819137573s
Interpretability | Number of blank nodes check for Shoah victims? names took 1.9420504570007324s
Security | Check HTTPS for Shoah victims? names took 0.19560837745666504s
Interpretability | RDF structures check for Shoah victims? names took 0.25481700897216797s
Versatility | Serialization formats check for Shoah victims? names took 0.28345322608947754s
Availability | RDF dump link check for Shoah victims? names took 0.17627620697021484s
License | MR license check for Shoah victims? names took 0.3755614757537842s
License | HR license check for Shoah victims? names took 8.943399429321289s
Amount of data | Number of property check for Shoah victims? names took 0.12031984329223633s
Understandability | Number of label check for Shoah victims? names took 0.9776656627655029s
Understandability | URI regex check for Shoah victims? names took 0.3870120048522949s
Understandability | Vocabs check for Shoah victims? names took 0.10369753837585449s
Verifiability | Authors check for Shoah victims? names took 0.1437230110168457s
Verifiability | Publishers check for Shoah victims? names took 0.179396390914917s
Performance | Throughput check for Shoah victims? names took 10.377877950668335s
Amount of data | Check the number of entities for Shoah victims? names took 7.534027099609375e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.08494234085083008s
Interlinking | sameAs chians check for Shoah victims? names took 0.09800076484680176s
Interlinking | skos check for Shoah victims? names took 0.188096284866333s
Interlinking | skos check for Shoah victims? names took 0.08541369438171387s
Timeliness | dataset update frequency check for Shoah victims? names took 0.16608715057373047s
Currency | Creation date check for Shoah victims? names took 0.1549851894378662s
Currency | Modification date check for Shoah victims? names took 0.18212628364562988s
Rep.Conc. | URIs length for Shoah victims? names took 2.475684404373169s
Interoperability | New vocabularies check for Shoah victims? names took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.09992361068725586s
Accuracy | Check Functional Property for Shoah victims? names took 0.10807228088378906s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.06441164016723633s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.38184452056884766s
Accuracy | Check White space in annotation for Shoah victims? names took 0.027292251586914062s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.029432296752929688s
Consistency | Disjoint class check for Shoah victims? names took 0.1574857234954834s
Consistency | Check Misplaced properties for Shoah victims? names took 1.9248089790344238s
Consistency | Misplaced classes for Shoah victims? names took 0.18648362159729004s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.5917816162109375s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.2945661544799805s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.140075445175171s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.034414052963256836s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.12146401405334473s
Security | Sign check for Shoah victims? names took 0.3374147415161133s
Availability | Check URIs Dereferenciability for Shoah victims? names took 837.0797743797302s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.48215436935424805s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.021688222885131836s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.6689300537109375e-06s
Believability | Calculation of trust value for Shoah victims? names took 1.2159347534179688e-05s
INFO | --- Analysis for shoah-victims-names took 953.1127920150757s
Availability | SPARQL endpoint availability check for Person took 4.1484832763671875e-05s
Availability | VoID file availability check for Person took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for Person took 0.2748281955718994s
Reputation | Calculation of the PageRank for Person took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for Person took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Person took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Person took 3.1948089599609375e-05s
Believability | Calculation of trust value for Person took 1.049041748046875e-05s
INFO | --- Analysis for Shripriya_Dubey took 2.4352970123291016s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 8.58306884765625e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.2628798484802246s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 3.075599670410156e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 7.62939453125e-06s
INFO | --- Analysis for Shutterstock took 2.4295997619628906s
Availability | SPARQL endpoint availability check for SIMPLE took 4.363059997558594e-05s
Availability | VoID file availability check for SIMPLE took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.27212977409362793s
Reputation | Calculation of the PageRank for SIMPLE took 0.021692991256713867s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.673004150390625e-05s
Believability | Calculation of trust value for SIMPLE took 1.049041748046875e-05s
INFO | --- Analysis for simple took 7.941057205200195s
Availability | SPARQL endpoint availability check for SITC-V4 took 25.204164266586304s
Availability | VoID file availability check for SITC-V4 took 0.0007469654083251953s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.26921653747558594s
Reputation | Calculation of the PageRank for SITC-V4 took 0.02196335792541504s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.4345855712890625e-05s
Believability | Calculation of trust value for SITC-V4 took 9.059906005859375e-06s
INFO | --- Analysis for sitc-v4 took 123.47691130638123s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 8.797645568847656e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.26702260971069336s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020748615264892578s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.506111145019531e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.0251998901367188e-05s
INFO | --- Analysis for sli_galnet_rdf took 12.691223382949829s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.220008850097656e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.3275797367095947s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.021016359329223633s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.314018249511719e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 1.3113021850585938e-05s
INFO | --- Analysis for slideshare2rdf took 2.6004886627197266s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.4402890205383301s
Availability | VoID file availability check for Linked Stage Graph took 0.0004756450653076172s
Extra | Recovery of all triples for Linked Stage Graph took 1.8347094058990479s
Performance | Total latancy measurement for Linked Stage Graph took 0.9736971855163574s
Amount of data | Number of triples check for Linked Stage Graph took 0.20957374572753906s
Interoperability | New terms check for Linked Stage Graph took 1.5750007629394531s
Versatility | Languages check for Linked Stage Graph took 0.6427874565124512s
Interpretability | Number of blank nodes check for Linked Stage Graph took 0.27066755294799805s
Security | Check HTTPS for Linked Stage Graph took 0.1273963451385498s
Interpretability | RDF structures check for Linked Stage Graph took 0.26210832595825195s
Versatility | Serialization formats check for Linked Stage Graph took 0.2546696662902832s
Availability | RDF dump link check for Linked Stage Graph took 0.1948070526123047s
License | MR license check for Linked Stage Graph took 0.3107762336730957s
License | HR license check for Linked Stage Graph took 1.7571165561676025s
Amount of data | Number of property check for Linked Stage Graph took 0.20136642456054688s
Understandability | Number of label check for Linked Stage Graph took 0.34544968605041504s
Understandability | URI regex check for Linked Stage Graph took 0.4177052974700928s
Understandability | Vocabs check for Linked Stage Graph took 0.19782280921936035s
Verifiability | Authors check for Linked Stage Graph took 0.21346235275268555s
Verifiability | Publishers check for Linked Stage Graph took 0.2096540927886963s
Performance | Throughput check for Linked Stage Graph took 11.533811569213867s
Amount of data | Check the number of entities for Linked Stage Graph took 6.985664367675781e-05s
Verifiability | Contribs. check for Linked Stage Graph took 0.19930720329284668s
Interlinking | sameAs chians check for Linked Stage Graph took 0.22224664688110352s
Interlinking | skos check for Linked Stage Graph took 0.22994446754455566s
Interlinking | skos check for Linked Stage Graph took 0.1960606575012207s
Timeliness | dataset update frequency check for Linked Stage Graph took 0.21365022659301758s
Currency | Creation date check for Linked Stage Graph took 0.4234578609466553s
Currency | Modification date check for Linked Stage Graph took 0.4154541492462158s
Rep.Conc. | URIs length for Linked Stage Graph took 1.348780870437622s
Interoperability | New vocabularies check for Linked Stage Graph took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Linked Stage Graph took 0.19597172737121582s
Accuracy | Check Functional Property for Linked Stage Graph took 0.2112274169921875s
Accuracy | Check Inverse Functional Property for Linked Stage Graph took 0.32747864723205566s
Accuracy | Check Empty annotation labels for Linked Stage Graph took 0.7742335796356201s
Accuracy | Check White space in annotation for Linked Stage Graph took 0.023478269577026367s
Accuracy | Check Datatype consistency for Linked Stage Graph took 0.028276681900024414s
Consistency | Disjoint class check for Linked Stage Graph took 0.1941225528717041s
Consistency | Check Misplaced properties for Linked Stage Graph took 0.849520206451416s
Consistency | Misplaced classes for Linked Stage Graph took 0.5561752319335938s
Consistency | Check Ontology hijacking for Linked Stage Graph took 2.058156967163086s
Consistency | Check Invalid usage of undefined classes for Linked Stage Graph took 1.2943315505981445s
Consistency | Check Invalid usage of undefined properties for Linked Stage Graph took 1.7267863750457764s
Conciseness | Check Extensional conciseness for Linked Stage Graph took 0.025878429412841797s
Conciseness | Check Intensional conciseness for Linked Stage Graph took 0.5201003551483154s
Security | Sign check for Linked Stage Graph took 0.24419951438903809s
Availability | Check URIs Dereferenciability for Linked Stage Graph took 919.7845420837402s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.32036685943603516s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.021190881729125977s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 6.890296936035156e-05s
Interoperability | Check the re-using of existing vocabs for Linked Stage Graph took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Stage Graph took 1.0967254638671875e-05s
INFO | --- Analysis for slod took 982.0703375339508s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.6254334449768066s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0005059242248535156s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 118.84575915336609s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.8939530849456787s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 9.464398622512817s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 14.138474702835083s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.21261620521545s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 1.9062178134918213s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.2045152187347412s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 9.00118350982666s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.24317574501037598s
License | MR license check for Smart Points Of Interest @PSNC took 0.4656519889831543s
License | HR license check for Smart Points Of Interest @PSNC took 300.22089433670044s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.18021607398986816s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 1.8649556636810303s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 0.6586565971374512s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.33585166931152344s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.18070459365844727s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.2264690399169922s
Performance | Throughput check for Smart Points Of Interest @PSNC took 10.737407922744751s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 0.00010633468627929688s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.17980217933654785s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.1800851821899414s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.4517698287963867s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.42788124084472656s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 8.030115604400635s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.43795323371887207s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.22533154487609863s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 152.26259422302246s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.17734980583190918s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.2768678665161133s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.25801634788513184s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 43.089139223098755s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.6105380058288574s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.608518600463867s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.17862653732299805s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 86.04432845115662s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.044408798217773s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 39.55358576774597s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.314270257949829s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 86.32515835762024s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.686176061630249s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.5371809005737305s
Security | Sign check for Smart Points Of Interest @PSNC took 0.6458263397216797s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 9.101589441299438s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.7520902156829834s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.021693944931030273s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.0001049041748046875s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for Smart_POI_dataset took 2248.3825829029083s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 4.3617188930511475s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.26976490020751953s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.021113157272338867s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.647804260253906e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 1.049041748046875e-05s
INFO | --- Analysis for smartlink took 10.895928144454956s
Availability | SPARQL endpoint availability check for SNIK took 0.36350321769714355s
Availability | VoID file availability check for SNIK took 0.0005350112915039062s
Extra | Recovery of all triples for SNIK took 3.3336660861968994s
Performance | Total latancy measurement for SNIK took 0.8706932067871094s
Amount of data | Number of triples check for SNIK took 0.18906927108764648s
Interoperability | New terms check for SNIK took 1.4048469066619873s
Versatility | Languages check for SNIK took 0.21402692794799805s
Interpretability | Number of blank nodes check for SNIK took 0.19295287132263184s
Interpretability | RDF structures check for SNIK took 0.180755615234375s
Versatility | Serialization formats check for SNIK took 0.19415497779846191s
Availability | RDF dump link check for SNIK took 0.17143893241882324s
License | MR license check for SNIK took 0.2001328468322754s
License | HR license check for SNIK took 0.21185731887817383s
Amount of data | Number of property check for SNIK took 0.17798280715942383s
Understandability | Number of label check for SNIK took 0.19577836990356445s
Understandability | URI regex check for SNIK took 0.3522803783416748s
Understandability | Vocabs check for SNIK took 0.18427133560180664s
Verifiability | Authors check for SNIK took 0.20682549476623535s
Verifiability | Publishers check for SNIK took 0.1760859489440918s
Performance | Throughput check for SNIK took 10.462460041046143s
Amount of data | Check the number of entities for SNIK took 3.218650817871094e-05s
Verifiability | Contribs. check for SNIK took 0.1843557357788086s
Interlinking | sameAs chians check for SNIK took 0.1791365146636963s
Interlinking | skos check for SNIK took 0.1690690517425537s
Interlinking | skos check for SNIK took 0.18231630325317383s
Timeliness | dataset update frequency check for SNIK took 0.18861770629882812s
Currency | Creation date check for SNIK took 0.35308098793029785s
Currency | Modification date check for SNIK took 0.3630654811859131s
Rep.Conc. | URIs length for SNIK took 1.3874282836914062s
Interoperability | New vocabularies check for SNIK took 5.4836273193359375e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.18627667427062988s
Accuracy | Check Functional Property for SNIK took 0.17538070678710938s
Accuracy | Check Inverse Functional Property for SNIK took 0.17571020126342773s
Accuracy | Check Empty annotation labels for SNIK took 0.6016626358032227s
Accuracy | Check White space in annotation for SNIK took 0.027283906936645508s
Accuracy | Check Datatype consistency for SNIK took 0.21259641647338867s
Consistency | Disjoint class check for SNIK took 0.16852188110351562s
Consistency | Check Misplaced properties for SNIK took 0.6401462554931641s
Consistency | Misplaced classes for SNIK took 0.6511015892028809s
Consistency | Check Ontology hijacking for SNIK took 1.7591347694396973s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.2196593284606934s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.455254077911377s
Conciseness | Check Extensional conciseness for SNIK took 0.14916372299194336s
Conciseness | Check Intensional conciseness for SNIK took 0.3202395439147949s
Security | Sign check for SNIK took 0.18524432182312012s
Availability | Check URIs Dereferenciability for SNIK took 1571.4850344657898s
Completeness | Calculation of interlinking completeness for SNIK took 0.4772188663482666s
Reputation | Calculation of the PageRank for SNIK took 0.021324872970581055s
Interlinking | Calculation of Degree of Connection for SNIK took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for SNIK took 8.487701416015625e-05s
Interoperability | Check the re-using of existing vocabs for SNIK took 1.430511474609375e-06s
Believability | Calculation of trust value for SNIK took 1.5020370483398438e-05s
INFO | --- Analysis for snik took 1623.2984800338745s
Availability | SPARQL endpoint availability check for SocialLink took 0.6052014827728271s
Availability | VoID file availability check for SocialLink took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for SocialLink took 0.26459240913391113s
Reputation | Calculation of the PageRank for SocialLink took 0.02328968048095703s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.200241088867188e-05s
Believability | Calculation of trust value for SocialLink took 1.0013580322265625e-05s
INFO | --- Analysis for SocialLink took 4.193849325180054s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 9.274482727050781e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.27106189727783203s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.02416825294494629s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.52587890625e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0012030601501464844s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 4.124641418457031e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 1.3113021850585938e-05s
INFO | --- Analysis for SocialRoles took 9.725263595581055s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.17186999320983887s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0007181167602539062s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 15.053246259689331s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.4361133575439453s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.19543027877807617s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.4916410446166992s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.3120231628417969s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.17947125434875488s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.3014514446258545s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.47376298904418945s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.10713768005371094s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.6900403499603271s
License | MR license check for Social Semantic Web Thesaurus took 0.12984800338745117s
License | HR license check for Social Semantic Web Thesaurus took 0.09823274612426758s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.10778498649597168s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.1063995361328125s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.16118955612182617s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.10636401176452637s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.1087644100189209s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.10565972328186035s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.539155960083008s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 0.000110626220703125s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.10377049446105957s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.1065068244934082s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.11348962783813477s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.08128547668457031s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.08510422706604004s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.1639385223388672s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.18953871726989746s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.5688691139221191s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 423.1572768688202s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.18461394309997559s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.10640978813171387s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.07953810691833496s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.4323539733886719s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012132644653320312s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.10589098930358887s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.2991774082183838s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.10425186157226562s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.1039412021636963s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.4897782802581787s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.0001583099365234375s
Security | Sign check for Social Semantic Web Thesaurus took 0.08033227920532227s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 98.26469016075134s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.33135175704956055s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020797014236450195s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0006725788116455078s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.846687316894531e-05s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 463.7734670639038s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.4066696166992188e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 1150.4360570907593s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.31050872802734375s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0004687309265136719s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 123.90038704872131s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.8917016983032227s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.155590772628784s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 13.899340152740479s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.2311489582062s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.1961302757263184s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.26787638664245605s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.494566679000854s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3266918659210205s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.7061312198638916s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.2190647125244s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18183588981628418s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.528672695159912s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.39880919456481934s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.23531365394592285s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18609070777893066s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.24634814262390137s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 10.722471475601196s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 6.914138793945312e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.17872405052185059s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1846764087677002s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.40236759185791016s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.39733219146728516s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.936218023300171s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.45480799674987793s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2362349033355713s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 155.65550684928894s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1761476993560791s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.36667895317077637s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.17201638221740723s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 35.494957447052s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.6367685794830322s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.590021848678589s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1793365478515625s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 85.30126309394836s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.20515251159668s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 36.79917502403259s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.1974475383758545s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 86.55130076408386s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.6891655921936035s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4788191318511963s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.0486552715301514s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 10.092214584350586s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5823447704315186s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.021353721618652344s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.2636184692382812e-05s
INFO | --- Analysis for Soil_maps took 2240.0103702545166s
Availability | SPARQL endpoint availability check for terrorrist ontology took 8.559226989746094e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.2770071029663086s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.021008729934692383s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for terrorrist ontology took 1.2159347534179688e-05s
INFO | --- Analysis for somya_omer took 2.43485426902771s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.315376281738281e-05s
Availability | VoID file availability check for Sonclubcx took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.27425122261047363s
Reputation | Calculation of the PageRank for Sonclubcx took 0.022531747817993164s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.0967254638671875e-05s
Believability | Calculation of trust value for Sonclubcx took 1.3589859008789062e-05s
INFO | --- Analysis for sonclubcx took 3.667896032333374s
Availability | SPARQL endpoint availability check for SORS took 4.363059997558594e-05s
Availability | VoID file availability check for SORS took 0.0007071495056152344s
Completeness | Calculation of interlinking completeness for SORS took 0.2663726806640625s
Reputation | Calculation of the PageRank for SORS took 0.02097940444946289s
Interlinking | Calculation of Degree of Connection for SORS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for SORS took 4.76837158203125e-05s
Believability | Calculation of trust value for SORS took 9.059906005859375e-06s
INFO | --- Analysis for sors took 12.680610656738281s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 0.000102996826171875s
Availability | VoID file availability check for southampton-ac-uk took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.27172160148620605s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.02320098876953125s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 8.988380432128906e-05s
Believability | Calculation of trust value for southampton-ac-uk took 1.0013580322265625e-05s
INFO | --- Analysis for southampton-ac-uk took 3.760939598083496s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 2.9563915729522705s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.2701292037963867s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.020809650421142578s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 5.245208740234375e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 9.914353609085083s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 5.2928924560546875e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.27372217178344727s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.0207061767578125s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.131431579589844e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.0251998901367188e-05s
INFO | --- Analysis for southampton-ecs-eprints took 2.582730770111084s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.47235703468322754s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0004482269287109375s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 168.26942658424377s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.1186332702636719s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.14458966255188s
Interoperability | New terms check for Spanish Linguistic Datasets took 3.064464569091797s
Versatility | Languages check for Spanish Linguistic Datasets took 51.063393115997314s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.7081165313720703s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.21390366554260254s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 1.6865944862365723s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.2630887031555176s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.254955530166626s
License | MR license check for Spanish Linguistic Datasets took 0.26007890701293945s
License | HR license check for Spanish Linguistic Datasets took 0.37186694145202637s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.27318787574768066s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.29644179344177246s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.528203010559082s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.7198493480682373s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.27274036407470703s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.26305627822875977s
Performance | Throughput check for Spanish Linguistic Datasets took 16.14353084564209s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 6.961822509765625e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.25984883308410645s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.2682805061340332s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2785325050354004s
Interlinking | skos check for Spanish Linguistic Datasets took 0.20754194259643555s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.291363000869751s
Currency | Creation date check for Spanish Linguistic Datasets took 1.3072285652160645s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5637805461883545s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 605.9137098789215s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.2784872055053711s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.7657520771026611s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.26587915420532227s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.8703141212463379s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.01038050651550293s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.532247304916382s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.2662630081176758s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.612045764923096s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.304296970367432s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 1598.6687989234924s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.359858512878418s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 12.160670518875122s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.8324520587921143s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.29148221015930176s
Security | Sign check for Spanish Linguistic Datasets took 0.27516651153564453s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 9.995392084121704s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.5323948860168457s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.021454334259033203s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.24249267578125e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 2.1457672119140625e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 1.4781951904296875e-05s
INFO | --- Analysis for spanish-linguistic-datasets took 2543.8246569633484s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.048822641372680664s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.2677462100982666s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.02250385284423828s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.744529724121094e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 8.344650268554688e-06s
INFO | --- Analysis for sparql-endpoint-status took 2.5098798274993896s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.124641418457031e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.26593446731567383s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.020786285400390625s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.296966552734375e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 7.62939453125e-06s
INFO | --- Analysis for springernaturescigraph took 2.8843166828155518s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 8.797645568847656e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.2623939514160156s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.022488117218017578s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 2.956390380859375e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.0013580322265625e-05s
INFO | --- Analysis for srcmf took 7.033863067626953s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.3091399669647217s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0005030632019042969s
Extra | Recovery of all triples for Lexicon of Syntactic and Semantic Framework took 1.0942444801330566s
Performance | Total latancy measurement for Lexicon of Syntactic and Semantic Framework took 0.8065416812896729s
Amount of data | Number of triples check for Lexicon of Syntactic and Semantic Framework took 0.31710243225097656s
Interoperability | New terms check for Lexicon of Syntactic and Semantic Framework took 1.6148977279663086s
Versatility | Languages check for Lexicon of Syntactic and Semantic Framework took 0.4459261894226074s
Interpretability | Number of blank nodes check for Lexicon of Syntactic and Semantic Framework took 0.4186239242553711s
Security | Check HTTPS for Lexicon of Syntactic and Semantic Framework took 0.07854843139648438s
Interpretability | RDF structures check for Lexicon of Syntactic and Semantic Framework took 0.13531017303466797s
Versatility | Serialization formats check for Lexicon of Syntactic and Semantic Framework took 0.13226652145385742s
Availability | RDF dump link check for Lexicon of Syntactic and Semantic Framework took 0.1327974796295166s
License | MR license check for Lexicon of Syntactic and Semantic Framework took 0.1676793098449707s
License | HR license check for Lexicon of Syntactic and Semantic Framework took 0.13677477836608887s
Amount of data | Number of property check for Lexicon of Syntactic and Semantic Framework took 0.17435073852539062s
Understandability | Number of label check for Lexicon of Syntactic and Semantic Framework took 0.16815590858459473s
Understandability | URI regex check for Lexicon of Syntactic and Semantic Framework took 0.39379262924194336s
Understandability | Vocabs check for Lexicon of Syntactic and Semantic Framework took 0.13980388641357422s
Verifiability | Authors check for Lexicon of Syntactic and Semantic Framework took 0.13146090507507324s
Verifiability | Publishers check for Lexicon of Syntactic and Semantic Framework took 0.13047337532043457s
Performance | Throughput check for Lexicon of Syntactic and Semantic Framework took 11.757792711257935s
Amount of data | Check the number of entities for Lexicon of Syntactic and Semantic Framework took 6.747245788574219e-05s
Verifiability | Contribs. check for Lexicon of Syntactic and Semantic Framework took 0.1313185691833496s
Interlinking | sameAs chians check for Lexicon of Syntactic and Semantic Framework took 0.13759613037109375s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.16484880447387695s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.1946558952331543s
Timeliness | dataset update frequency check for Lexicon of Syntactic and Semantic Framework took 0.14034485816955566s
Currency | Creation date check for Lexicon of Syntactic and Semantic Framework took 0.5120236873626709s
Currency | Modification date check for Lexicon of Syntactic and Semantic Framework took 0.33150267601013184s
Rep.Conc. | URIs length for Lexicon of Syntactic and Semantic Framework took 0.556793212890625s
Interoperability | New vocabularies check for Lexicon of Syntactic and Semantic Framework took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Lexicon of Syntactic and Semantic Framework took 0.14417648315429688s
Accuracy | Check Functional Property for Lexicon of Syntactic and Semantic Framework took 0.18469572067260742s
Accuracy | Check Inverse Functional Property for Lexicon of Syntactic and Semantic Framework took 0.13420867919921875s
Accuracy | Check Empty annotation labels for Lexicon of Syntactic and Semantic Framework took 0.1387784481048584s
Accuracy | Check White space in annotation for Lexicon of Syntactic and Semantic Framework took 0.00030803680419921875s
Accuracy | Check Datatype consistency for Lexicon of Syntactic and Semantic Framework took 0.0352628231048584s
Consistency | Disjoint class check for Lexicon of Syntactic and Semantic Framework took 0.13484835624694824s
Consistency | Check Misplaced properties for Lexicon of Syntactic and Semantic Framework took 0.27388644218444824s
Consistency | Misplaced classes for Lexicon of Syntactic and Semantic Framework took 0.18504548072814941s
Consistency | Check Ontology hijacking for Lexicon of Syntactic and Semantic Framework took 1.3387446403503418s
Consistency | Check Invalid usage of undefined classes for Lexicon of Syntactic and Semantic Framework took 1.1618683338165283s
Consistency | Check Invalid usage of undefined properties for Lexicon of Syntactic and Semantic Framework took 1.3078656196594238s
Conciseness | Check Extensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.02106475830078125s
Conciseness | Check Intensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.17919445037841797s
Security | Sign check for Lexicon of Syntactic and Semantic Framework took 0.25734806060791016s
Availability | Check URIs Dereferenciability for Lexicon of Syntactic and Semantic Framework took 258.5686688423157s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 1.2767560482025146s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 5.2928924560546875e-05s
Interoperability | Check the re-using of existing vocabs for Lexicon of Syntactic and Semantic Framework took 1.6689300537109375e-06s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 8.344650268554688e-06s
INFO | --- Analysis for ssf took 302.04449462890625s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.220008850097656e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.00030112266540527344s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.26309847831726074s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.0208432674407959s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.695487976074219e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 8.344650268554688e-06s
INFO | --- Analysis for st-andrews-resource-lists took 2.654819965362549s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 8.535385131835938e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0003528594970703125s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.271712064743042s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.021024227142333984s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.552436828613281e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 8.106231689453125e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 2.8578600883483887s
Availability | SPARQL endpoint availability check for Stammbuch took 7.462501525878906e-05s
Availability | VoID file availability check for Stammbuch took 0.00021576881408691406s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.2629549503326416s
Reputation | Calculation of the PageRank for Stammbuch took 0.02159595489501953s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 3.075599670410156e-05s
Believability | Calculation of trust value for Stammbuch took 5.7220458984375e-06s
INFO | --- Analysis for Stammbuch took 2.405362844467163s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.0021724700927734s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0008196830749511719s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.25820088386535645s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.021048307418823242s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010442733764648438s
Believability | Calculation of trust value for statistics.data.gov.uk took 4.76837158203125e-06s
INFO | --- Analysis for statistics-data-gov-uk took 3.6155812740325928s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 8.392333984375e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.2724645137786865s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.022423267364501953s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00010371208190917969s
Believability | Calculation of trust value for statusnet-1w6-org took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-1w6-org took 3.82230544090271s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.26540303230285645s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.021538734436035156s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.270408630371094e-05s
Believability | Calculation of trust value for statusnet-20100-org took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-20100-org took 2.4596099853515625s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0003833770751953125s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.2560558319091797s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020934104919433594s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 6.723403930664062e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.78572678565979s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.2656412124633789s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.022791385650634766s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 8.440017700195312e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.465714931488037s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 8.344650268554688e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.26335668563842773s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.02118086814880371s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.655952453613281e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-belfalas-org took 2.469924211502075s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0007872581481933594s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.27591514587402344s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.02168130874633789s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00011610984802246094s
Believability | Calculation of trust value for statusnet-bka-li took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-bka-li took 12.593452215194702s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 7.104873657226562e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.27316999435424805s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.021378278732299805s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 4.57763671875e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.332603931427002s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.2637746334075928s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.021098613739013672s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.982948303222656e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-ced117-net took 3.733949661254883s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.26453351974487305s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020948410034179688s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.14984130859375e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.547607421875s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 8.344650268554688e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.27091217041015625s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.023129701614379883s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011157989501953125s
Believability | Calculation of trust value for statusnet-chromic-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-chromic-org took 2.613955497741699s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 0.00010466575622558594s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.27240920066833496s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.021015644073486328s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 8.034706115722656e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-cooleysekula-net took 5.9217164516448975s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 5.745887756347656e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.266920804977417s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.021234512329101562s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.507469177246094e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.5002944469451904s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.863739013671875e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0003268718719482422s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.26064276695251465s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.02068018913269043s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.890296936035156e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 2.9817824363708496s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.2696239948272705s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.02110457420349121s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010156631469726562s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.5205092430114746s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 7.152557373046875e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.26066160202026367s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.020987510681152344s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.079673767089844e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.3796722888946533s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 3.981590270996094e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.26111650466918945s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.02108311653137207s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.173683166503906e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 5.245208740234375e-06s
INFO | --- Analysis for statusnet-doomicile-de took 4.03528618812561s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.029273986816406e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.2653985023498535s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020900964736938477s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.413459777832031e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 5.4836273193359375e-06s
INFO | --- Analysis for statusnet-dtdns-net took 22.38408660888672s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.00020575523376464844s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.25954294204711914s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.719329833984375e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.3708040714263916s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 0.00011658668518066406s
Availability | VoID file availability check for statusnet-exdc-net took 0.0012497901916503906s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.2619435787200928s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.021348953247070312s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.462501525878906e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-exdc-net took 2.4891510009765625s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.256591796875s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.02073979377746582s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.274482727050781e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-fcac-com took 2.8236117362976074s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.00042629241943359375s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.26132750511169434s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020841360092163086s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.5789947509765625e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 3.0782809257507324s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.00029778480529785156s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.26842379570007324s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.021053552627563477s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00018167495727539062s
Believability | Calculation of trust value for statusnet-fragdev-com took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-fragdev-com took 3.26436710357666s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.029273986816406e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.28331875801086426s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.021633625030517578s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.605552673339844e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 4.76837158203125e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.486467123031616s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.00030612945556640625s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.2559082508087158s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.021179676055908203s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.0001087188720703125s
Believability | Calculation of trust value for statusnet-gegeweb-org took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.485974073410034s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0002155303955078125s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.26813220977783203s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.02113175392150879s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.914138793945312e-05s
Believability | Calculation of trust value for statusnet-glou-org took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-glou-org took 2.414362907409668s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.00022220611572265625s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.2582125663757324s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.021081924438476562s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00012373924255371094s
Believability | Calculation of trust value for statusnet-gomertronic-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.3774538040161133s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 8.58306884765625e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.268695592880249s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.020993709564208984s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010609626770019531s
Believability | Calculation of trust value for statusnet-hackerposse-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.8611838817596436s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 8.797645568847656e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.2692232131958008s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.76837158203125e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-hii-co-il took 3.743109703063965s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.2744302749633789s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.0208895206451416s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.679794311523438e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 2.806550979614258s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 8.082389831542969e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.2713649272918701s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.02061772346496582s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 5.91278076171875e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-imirhil-fr took 2.4854633808135986s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 9.417533874511719e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2733430862426758s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.020597457885742188s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.0531158447265625e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-integralblue-com took 2.6332223415374756s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0008115768432617188s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.26709723472595215s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.021057844161987305s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 6.008148193359375e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.459680795669556s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 8.463859558105469e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.2697021961212158s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.02122974395751953s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011610984802246094s
Believability | Calculation of trust value for statusnet-jonkman-ca took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 3.309905767440796s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 8.630752563476562e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.2697901725769043s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.021033763885498047s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.632110595703125e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 2.479374647140503s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 8.320808410644531e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.27073216438293457s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.02284979820251465s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 5.1021575927734375e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.4801197052001953s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 8.296966552734375e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.2705080509185791s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.022530078887939453s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.886222839355469e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-kenzoid-com took 3.404062032699585s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 8.916854858398438e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.2663295269012451s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.02266669273376465s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.62939453125e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-keuser-fr took 2.4534497261047363s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.26167726516723633s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.022637605667114258s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.982948303222656e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.526186466217041s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.2739734649658203s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.020888805389404297s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.413459777832031e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-lebsanft-org took 2.5985336303710938s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 8.654594421386719e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.2689015865325928s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020989179611206055s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.632110595703125e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.608386754989624s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 8.320808410644531e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.2649095058441162s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.02191019058227539s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011706352233886719s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.4850118160247803s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 8.654594421386719e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.25787854194641113s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02097010612487793s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.6743621826171875e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-ludost-net took 3.6939589977264404s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.2622861862182617s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.02099776268005371s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 0.00010371208190917969s
Believability | Calculation of trust value for statusnet-lydiastench-com took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.454089641571045s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 8.535385131835938e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.263704776763916s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.021507740020751953s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.348241090774536s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.27368593215942383s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.021254777908325195s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00014901161193847656s
Believability | Calculation of trust value for statusnet-macno-org took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-macno-org took 2.5019445419311523s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0004241466522216797s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.26325154304504395s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.02131485939025879s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.67572021484375e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.5245237350463867s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 8.20159912109375e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0007817745208740234s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.2692558765411377s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.02130436897277832s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.821487426757812e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-maymay-net took 42.48941087722778s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.2717282772064209s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.02255535125732422s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00015974044799804688s
Believability | Calculation of trust value for statusnet-morphtown-de took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.4498887062072754s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.27004361152648926s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.022249221801757812s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.918212890625e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-mrblog-nl took 2.6130881309509277s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 8.416175842285156e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.2681732177734375s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.023080825805664062s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.4489290714263916s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 0.00010228157043457031s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.2650747299194336s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020804882049560547s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.4836273193359375e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-my-status-tk took 2.5781195163726807s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.27405428886413574s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.021517038345336914s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00010967254638671875s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.4596383571624756s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.31112074851989746s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.021202564239501953s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 6.127357482910156e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.6592564582824707s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.2695338726043701s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.02235555648803711s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.747245788574219e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.523635149002075s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 5.125999450683594e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.27193570137023926s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.02116537094116211s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 9.107589721679688e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.490368127822876s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 8.296966552734375e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.27394556999206543s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.022617578506469727s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.982948303222656e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-panda-id-au took 2.950096845626831s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.00043773651123046875s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.27374863624572754s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.021097660064697266s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.5367431640625e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.5617330074310303s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.26082587242126465s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.021791934967041016s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 8.082389831542969e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-planet-libre-org took 2.4687979221343994s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 8.416175842285156e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.27299952507019043s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.020749330520629883s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00022721290588378906s
Believability | Calculation of trust value for statusnet-postblue-info took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-postblue-info took 2.6576530933380127s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.26032090187072754s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.020775556564331055s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.580352783203125e-05s
Believability | Calculation of trust value for statusnet-progval-net took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-progval-net took 2.5241215229034424s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.2771756649017334s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.021015167236328125s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.000110626220703125s
Believability | Calculation of trust value for statusnet-qdnx-org took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-qdnx-org took 2.9925076961517334s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 8.344650268554688e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0011911392211914062s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.28549909591674805s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.02332615852355957s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.246566772460938e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-qth-fr took 3.3434765338897705s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 0.00014925003051757812s
Availability | VoID file availability check for statusnet-quitter-se took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.2614865303039551s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00021791458129882812s
Believability | Calculation of trust value for statusnet-quitter-se took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-quitter-se took 5.583040237426758s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.26729464530944824s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.0229489803314209s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 9.775161743164062e-05s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.7013561725616455s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 8.606910705566406e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.27273011207580566s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.02085709571838379s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.7697296142578125e-05s
Believability | Calculation of trust value for statusnet-recit-org took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-recit-org took 4.206026792526245s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.001262664794921875s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.28621673583984375s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.022730350494384766s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.0001480579376220703s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-russwurm-org took 3.2650203704833984s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0006868839263916016s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.29799509048461914s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.021564483642578125s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.559226989746094e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-samnoble-org took 4.744321346282959s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 8.630752563476562e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.26705169677734375s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.021690845489501953s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.249282836914062e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-schiessle-org took 2.5889365673065186s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 8.630752563476562e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.2649548053741455s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.02064371109008789s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 0.00010132789611816406s
Believability | Calculation of trust value for statusnet-scoffoni-net took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-scoffoni-net took 2.5376648902893066s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 8.344650268554688e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.2836918830871582s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020807266235351562s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.079673767089844e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-sebseb01-net took 2.5609638690948486s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.2784583568572998s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020920276641845703s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.295608520507812e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-shnoulle-net took 3.182097911834717s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 8.749961853027344e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0013778209686279297s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.26918458938598633s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.021306753158569336s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00021600723266601562s
Believability | Calculation of trust value for statusnet-skilledtests-com took 5.8650970458984375e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 4.159196615219116s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 0.0001308917999267578s
Availability | VoID file availability check for statusnet-somsants-net took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2733292579650879s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.020636796951293945s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010538101196289062s
Believability | Calculation of trust value for statusnet-somsants-net took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-somsants-net took 2.5039784908294678s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 9.107589721679688e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.26823973655700684s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.02062201499938965s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00013256072998046875s
Believability | Calculation of trust value for statusnet-soucy-cc took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-soucy-cc took 3.986703634262085s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 8.249282836914062e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.26936769485473633s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.02195572853088379s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0008244514465332031s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 7.033348083496094e-05s
Believability | Calculation of trust value for statusnet-spip-org took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-spip-org took 3.3303029537200928s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 6.103515625e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0008099079132080078s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.27295947074890137s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.022272348403930664s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.365776062011719e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-spraci-org took 5.651970386505127s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.269331693649292s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00010776519775390625s
Believability | Calculation of trust value for statusnet-ssweeny-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-ssweeny-net took 5.493746042251587s
Availability | SPARQL endpoint availability check for statusnet-status-net took 8.416175842285156e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.27512693405151367s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.02085423469543457s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0009362697601318359s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00024509429931640625s
Believability | Calculation of trust value for statusnet-status-net took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-status-net took 3.394577741622925s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 9.202957153320312e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2635774612426758s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.316734313964844e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.4492220878601074s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 8.869171142578125e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.00041556358337402344s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.26925230026245117s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.0229799747467041s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.632110595703125e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.4416067600250244s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.2692430019378662s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.02142190933227539s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00012612342834472656s
Believability | Calculation of trust value for statusnet-thelovebug-org took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-thelovebug-org took 2.498716354370117s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 8.392333984375e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0007891654968261719s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.27341365814208984s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.02170538902282715s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.534027099609375e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-thornton2-com took 6.679397344589233s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 9.417533874511719e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.26173901557922363s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.02120208740234375s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00010991096496582031s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.7106902599334717s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.2682008743286133s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.02189350128173828s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 4.0531158447265625e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-tl1n-com took 3.422605514526367s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.26113176345825195s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.651878356933594e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.621302366256714s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.2669558525085449s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.02026653289794922s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.933906555175781e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.669257402420044s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.1961669921875e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.27668237686157227s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020374298095703125s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 3.170967102050781e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 8.106231689453125e-06s
INFO | --- Analysis for steak took 2.6724698543548584s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 4.267692565917969e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.2727525234222412s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.020962953567504883s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.53131103515625e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 9.5367431640625e-06s
INFO | --- Analysis for stitch-rameau took 3.9353270530700684s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.76578688621521s
Availability | VoID file availability check for Stone Tech Square took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.2707231044769287s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.3589859008789062e-05s
Believability | Calculation of trust value for Stone Tech Square took 1.239776611328125e-05s
INFO | --- Analysis for stone-tech-square-data took 4.512885808944702s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.43341493606567383s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0007381439208984375s
Extra | Recovery of all triples for STW Thesaurus for Economics took 17.350138187408447s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.035616159439087s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.7027251720428467s
Interoperability | New terms check for STW Thesaurus for Economics took 1.4146792888641357s
Versatility | Languages check for STW Thesaurus for Economics took 1.5611870288848877s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.536306619644165s
Security | Check HTTPS for STW Thesaurus for Economics took 0.1263291835784912s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.2231147289276123s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.21730494499206543s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.24230241775512695s
License | MR license check for STW Thesaurus for Economics took 0.2151660919189453s
License | HR license check for STW Thesaurus for Economics took 2.428759813308716s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.2240581512451172s
Understandability | Number of label check for STW Thesaurus for Economics took 0.6402974128723145s
Understandability | URI regex check for STW Thesaurus for Economics took 0.4406414031982422s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.21929216384887695s
Verifiability | Authors check for STW Thesaurus for Economics took 0.2199242115020752s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.2142772674560547s
Performance | Throughput check for STW Thesaurus for Economics took 11.689344882965088s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7100546360015869s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.2164757251739502s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.24503803253173828s
Interlinking | skos check for STW Thesaurus for Economics took 0.31383419036865234s
Interlinking | skos check for STW Thesaurus for Economics took 0.2951228618621826s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.2235116958618164s
Currency | Creation date check for STW Thesaurus for Economics took 0.45502161979675293s
Currency | Modification date check for STW Thesaurus for Economics took 0.4910318851470947s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 8.475177526473999s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 2.8300647735595703s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.41887974739074707s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.236403226852417s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.21514129638671875s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 5.380809783935547s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0265965461730957s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.3226873874664307s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.23329687118530273s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.2840771675109863s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 1.5867640972137451s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.2067515850067139s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.2484047412872314s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.631197452545166s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.2329092025756836s
Security | Sign check for STW Thesaurus for Economics took 0.21661710739135742s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 2067.1400480270386s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.44948792457580566s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.02227783203125s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.0001308917999267578s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 3.4147496223449707s
Believability | Calculation of trust value for STW Thesaurus for Economics took 1.1920928955078125e-05s
INFO | --- Analysis for stw-thesaurus-for-economics took 2164.784788608551s
Availability | SPARQL endpoint availability check for SudershanTech took 8.273124694824219e-05s
Availability | VoID file availability check for SudershanTech took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.26299047470092773s
Reputation | Calculation of the PageRank for SudershanTech took 0.021013498306274414s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.2901763916015625e-05s
Believability | Calculation of trust value for SudershanTech took 1.0013580322265625e-05s
INFO | --- Analysis for SudershanTech took 2.419799327850342s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.7639570236206055s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.26644349098205566s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.022701501846313477s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.935264587402344e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 1.0728836059570312e-05s
INFO | --- Analysis for sudocfr took 7.087616920471191s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 0.9921340942382812s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0006260871887207031s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 31.90335774421692s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.615537405014038s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.7686553001403809s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 2.665001630783081s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 3.5898029804229736s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.4687740802764893s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5238559246063232s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5248622894287109s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.6107456684112549s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5071611404418945s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 10.42318868637085s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.5617372989654541s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.6855590343475342s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.03725266456604s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5278196334838867s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5248563289642334s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5523483753204346s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.432649850845337s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 3.2901763916015625e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5625264644622803s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5576574802398682s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6379504203796387s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5729973316192627s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.543135404586792s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.0353310108184814s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.0357582569122314s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 45.26054334640503s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5296721458435059s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.506178617477417s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5058600902557373s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 3.4194700717926025s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.3722209930419922s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.525496244430542s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 34.7294340133667s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.274875402450562s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.42380809783936s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 26.581891298294067s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.9381487369537354s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.5267558097839355s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5263843536376953s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4343.417407751083s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.6020925045013428s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.021121501922607422s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0006871223449707031s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 8.130073547363281e-05s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 1.1682510375976562e-05s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 7845.386040687561s
Availability | SPARQL endpoint availability check for Surge Radio took 8.916854858398438e-05s
Availability | VoID file availability check for Surge Radio took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.2649815082550049s
Reputation | Calculation of the PageRank for Surge Radio took 0.02120351791381836s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.559226989746094e-05s
Believability | Calculation of trust value for Surge Radio took 1.0251998901367188e-05s
INFO | --- Analysis for surge-radio took 3.4614291191101074s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 8.559226989746094e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.26918768882751465s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.7670135498046875e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 1.2874603271484375e-05s
INFO | --- Analysis for SWAT took 85.81713461875916s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.553794860839844e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.399611234664917s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.2739369869232178s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020559310913085938s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.699562072753906e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 1.049041748046875e-05s
INFO | --- Analysis for swedish-open-cultural-heritage took 5.47599196434021s
Availability | SPARQL endpoint availability check for SweFN-RDF took 0.9557592868804932s
Availability | VoID file availability check for SweFN-RDF took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.2749207019805908s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for SweFN-RDF took 1.2636184692382812e-05s
INFO | --- Analysis for swefn-rdf took 5.414146900177002s
Availability | SPARQL endpoint availability check for SwetoDblp took 8.821487426757812e-05s
Availability | VoID file availability check for SwetoDblp took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.2757585048675537s
Reputation | Calculation of the PageRank for SwetoDblp took 0.021268367767333984s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.910064697265625e-05s
Believability | Calculation of trust value for SwetoDblp took 1.239776611328125e-05s
INFO | --- Analysis for sweto-dblp took 22.779800415039062s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.47267961502075195s
Availability | VoID file availability check for Swift Vocabulary took 0.0005929470062255859s
Extra | Recovery of all triples for Swift Vocabulary took 2.003821611404419s
Performance | Total latancy measurement for Swift Vocabulary took 0.9311521053314209s
Amount of data | Number of triples check for Swift Vocabulary took 0.157210111618042s
Interoperability | New terms check for Swift Vocabulary took 1.2920210361480713s
Versatility | Languages check for Swift Vocabulary took 0.1503126621246338s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.18589043617248535s
Interpretability | RDF structures check for Swift Vocabulary took 0.1934676170349121s
Versatility | Serialization formats check for Swift Vocabulary took 0.1952824592590332s
Availability | RDF dump link check for Swift Vocabulary took 0.1881875991821289s
License | MR license check for Swift Vocabulary took 0.1936349868774414s
License | HR license check for Swift Vocabulary took 0.19228124618530273s
Amount of data | Number of property check for Swift Vocabulary took 0.1883246898651123s
Understandability | Number of label check for Swift Vocabulary took 0.19642400741577148s
Understandability | URI regex check for Swift Vocabulary took 0.37564706802368164s
Understandability | Vocabs check for Swift Vocabulary took 0.18880653381347656s
Verifiability | Authors check for Swift Vocabulary took 0.18870806694030762s
Verifiability | Publishers check for Swift Vocabulary took 0.1891188621520996s
Performance | Throughput check for Swift Vocabulary took 11.121157884597778s
Amount of data | Check the number of entities for Swift Vocabulary took 7.081031799316406e-05s
Verifiability | Contribs. check for Swift Vocabulary took 0.18788838386535645s
Interlinking | sameAs chians check for Swift Vocabulary took 0.18606352806091309s
Interlinking | skos check for Swift Vocabulary took 0.1875619888305664s
Interlinking | skos check for Swift Vocabulary took 0.18805742263793945s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.19081377983093262s
Currency | Creation date check for Swift Vocabulary took 0.3777346611022949s
Currency | Modification date check for Swift Vocabulary took 0.3803141117095947s
Rep.Conc. | URIs length for Swift Vocabulary took 0.7749371528625488s
Interoperability | New vocabularies check for Swift Vocabulary took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.18703556060791016s
Accuracy | Check Functional Property for Swift Vocabulary took 0.18623757362365723s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.18812894821166992s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.30994343757629395s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.004412412643432617s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.03656959533691406s
Consistency | Disjoint class check for Swift Vocabulary took 0.1860647201538086s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.41422104835510254s
Consistency | Misplaced classes for Swift Vocabulary took 0.25923657417297363s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.3312108516693115s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.1101200580596924s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.2663521766662598s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.025688648223876953s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.15290379524230957s
Security | Sign check for Swift Vocabulary took 0.1556699275970459s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 1000.6178059577942s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.48990368843078613s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.021381378173828125s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 0.0001285076141357422s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 1.9073486328125e-06s
Believability | Calculation of trust value for Swift Vocabulary took 7.62939453125e-06s
INFO | --- Analysis for Swift took 1046.1419928073883s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 7.486343383789062e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0003325939178466797s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.262493371963501s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.0040740966796875e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 7.3909759521484375e-06s
INFO | --- Analysis for symptoms-in-chinese took 3.5331685543060303s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.36220788955688477s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0003783702850341797s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.42737460136413574s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.772406816482544s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 7.7145538330078125s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 18.177923679351807s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.18636775016784668s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 3.433694362640381s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.09633159637451172s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.48595356941223145s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.1788644790649414s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.15647029876708984s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.2564728260040283s
License | HR license check for National Digital Data Archive of Hungary (partial) took 52.894827127456665s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.4335033893585205s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 36.01206636428833s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3195838928222656s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.17868733406066895s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.33045005798339844s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.1578531265258789s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 10.979915142059326s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 7.104873657226562e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 0.18135333061218262s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 0.3299863338470459s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 0.16468501091003418s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 0.15752625465393066s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 0.1627795696258545s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 0.3203468322753906s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 0.31638121604919434s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 60.5341112613678s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.15616536140441895s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.1659247875213623s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.1559457778930664s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.2039661407470703s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0021135807037353516s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0014371871948242188s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.15555167198181152s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 44.554752588272095s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.23065543174743652s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.3811771869659424s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.125164270401001s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 45.031795024871826s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.0018939971923828125s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.2966480255126953s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.15821146965026855s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 12.761958599090576s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.33234572410583496s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.022455215454101562s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 8.845329284667969e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 9.5367431640625e-07s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 1.1682510375976562e-05s
INFO | --- Analysis for sztaki-lod took 477.1893663406372s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.291534423828125e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.2690417766571045s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.022096872329711914s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.507469177246094e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 1.0251998901367188e-05s
INFO | --- Analysis for t4gm-info took 2.6702558994293213s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.410743713378906e-05s
Availability | VoID file availability check for tags2con delicious took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.2651097774505615s
Reputation | Calculation of the PageRank for tags2con delicious took 0.02102375030517578s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.00543212890625e-05s
Believability | Calculation of trust value for tags2con delicious took 1.2874603271484375e-05s
INFO | --- Analysis for tags2con-delicious took 44.63465619087219s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 263.3295953273773s
Availability | VoID file availability check for Taiwan geographic names took 0.0008413791656494141s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.29972028732299805s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.021688461303710938s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 6.29425048828125e-05s
Believability | Calculation of trust value for Taiwan geographic names took 1.1444091796875e-05s
INFO | --- Analysis for taiwan-geographic-names took 669.3790974617004s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 8.869171142578125e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.27143168449401855s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.02130413055419922s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 8.893013000488281e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 1.0251998901367188e-05s
INFO | --- Analysis for talis-openlibrary took 3.8266828060150146s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.8536579608917236s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.27288222312927246s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.02187943458557129s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00012111663818359375s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 1.1682510375976562e-05s
INFO | --- Analysis for taxonconcept took 13.06010389328003s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 8.606910705566406e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.2633199691772461s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.022922277450561523s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.153915405273438e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.239776611328125e-05s
INFO | --- Analysis for taxonconcept-assets took 2.8590078353881836s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 8.392333984375e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0012965202331542969s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.2660789489746094s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.020967960357666016s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.459785461425781e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 1.1682510375976562e-05s
INFO | --- Analysis for taxonconcept-occurences took 2.7973761558532715s
Availability | SPARQL endpoint availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 21.229438543319702s
Availability | VoID file availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0007884502410888672s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.2797739505767822s
Reputation | Calculation of the PageRank for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.021178483963012695s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 5.8650970458984375e-05s
Believability | Calculation of trust value for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.1444091796875e-05s
INFO | --- Analysis for taxref-ld took 75.0443046092987s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 261.95674562454224s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.2673835754394531s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.021230459213256836s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 4.029273986816406e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.1444091796875e-05s
INFO | --- Analysis for tcga took 540.4223475456238s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.34253382682800293s
Availability | VoID file availability check for TCGA Roadmap took 0.00035834312438964844s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.2677333354949951s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.021175861358642578s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.295608520507812e-05s
Believability | Calculation of trust value for TCGA Roadmap took 1.3589859008789062e-05s
INFO | --- Analysis for tcga-roadmap took 5.647009372711182s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.0690948963165283s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.29358458518981934s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.021656513214111328s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00010895729064941406s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for tcmgenedit_dataset took 137.87639689445496s
Availability | SPARQL endpoint availability check for TDS took 4.172325134277344e-05s
Availability | VoID file availability check for TDS took 0.0007607936859130859s
Completeness | Calculation of interlinking completeness for TDS took 0.26418447494506836s
Reputation | Calculation of the PageRank for TDS took 0.021260499954223633s
Interlinking | Calculation of Degree of Connection for TDS took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for TDS took 0.0009465217590332031s
Interlinking | Calculation of Clustering coefficient for TDS took 4.982948303222656e-05s
Believability | Calculation of trust value for TDS took 1.239776611328125e-05s
INFO | --- Analysis for tds took 4.619923114776611s
Availability | SPARQL endpoint availability check for TEKORD took 8.392333984375e-05s
Availability | VoID file availability check for TEKORD took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for TEKORD took 0.2708742618560791s
Reputation | Calculation of the PageRank for TEKORD took 0.021424055099487305s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.458427429199219e-05s
Believability | Calculation of trust value for TEKORD took 1.239776611328125e-05s
INFO | --- Analysis for tekord took 5.0510900020599365s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 1.7529370784759521s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0003342628479003906s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.26659250259399414s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.030612468719482422s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0010421276092529297s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.0001347064971923828s
Believability | Calculation of trust value for Telegraphis Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for telegraphis took 7.701976776123047s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 9.512901306152344e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.2669088840484619s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.021172285079956055s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 6.914138793945312e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 1.0251998901367188e-05s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 13.239118814468384s
Availability | SPARQL endpoint availability check for Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Ontology took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for Ontology took 0.2744121551513672s
Reputation | Calculation of the PageRank for Ontology took 0.021011829376220703s
Interlinking | Calculation of Degree of Connection for Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for Terrorist_attack took 2.9678566455841064s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.3392181396484375e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.2724592685699463s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.021392345428466797s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.1948089599609375e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 1.0013580322265625e-05s
INFO | --- Analysis for Terrorist_Attack_1 took 2.4182815551757812s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 4.1484832763671875e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.3267381191253662s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.021219968795776367s
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.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.123283386230469e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.049041748046875e-05s
INFO | --- Analysis for Tesla_Deaths took 4.306765079498291s
Availability | SPARQL endpoint availability check for test took 5.14984130859375e-05s
Availability | VoID file availability check for test took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for test took 0.2725191116333008s
Reputation | Calculation of the PageRank for test took 0.0209653377532959s
Interlinking | Calculation of Degree of Connection for test took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for test took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for test took 3.218650817871094e-05s
Believability | Calculation of trust value for test took 9.5367431640625e-06s
INFO | --- Analysis for test took 2.413428783416748s
Availability | SPARQL endpoint availability check for Test took 7.510185241699219e-05s
Availability | VoID file availability check for Test took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Test took 0.27038121223449707s
Reputation | Calculation of the PageRank for Test took 0.021082639694213867s
Interlinking | Calculation of Degree of Connection for Test took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Test took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Test took 3.075599670410156e-05s
Believability | Calculation of trust value for Test took 1.2159347534179688e-05s
INFO | --- Analysis for Test took 2.4116334915161133s
Availability | SPARQL endpoint availability check for test-svu took 20.176117658615112s
Availability | VoID file availability check for test-svu took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for test-svu took 0.2710120677947998s
Reputation | Calculation of the PageRank for test-svu took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for test-svu took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.0994415283203125e-05s
Believability | Calculation of trust value for test-svu took 1.1920928955078125e-05s
INFO | --- Analysis for test-svu took 52.61090040206909s
Availability | SPARQL endpoint availability check for Test took 8.58306884765625e-05s
Availability | VoID file availability check for Test took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Test took 0.26845741271972656s
Reputation | Calculation of the PageRank for Test took 0.020904064178466797s
Interlinking | Calculation of Degree of Connection for Test took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Test took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Test took 3.3855438232421875e-05s
Believability | Calculation of trust value for Test took 1.2636184692382812e-05s
INFO | --- Analysis for Test_ took 2.441190481185913s
Availability | SPARQL endpoint availability check for xxxxx took 261.6232829093933s
Availability | VoID file availability check for xxxxx took 0.0008320808410644531s
Completeness | Calculation of interlinking completeness for xxxxx took 0.3741579055786133s
Reputation | Calculation of the PageRank for xxxxx took 0.021242380142211914s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for xxxxx took 5.435943603515625e-05s
Believability | Calculation of trust value for xxxxx took 1.0967254638671875e-05s
INFO | --- Analysis for testee took 796.6953527927399s
Availability | SPARQL endpoint availability check for tharawat magazine took 4.1961669921875e-05s
Availability | VoID file availability check for tharawat magazine took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.27009010314941406s
Reputation | Calculation of the PageRank for tharawat magazine took 0.020924806594848633s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00010633468627929688s
Believability | Calculation of trust value for tharawat magazine took 9.775161743164062e-06s
INFO | --- Analysis for tharawat-magazine-com took 3.0427234172821045s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 1.492222785949707s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.2658100128173828s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.020790576934814453s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 2.956390380859375e-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 7.640367269515991s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 1.9692518711090088s
Availability | VoID file availability check for The European Library Open Dataset took 0.0006921291351318359s
Extra | Recovery of all triples for The European Library Open Dataset took 7.092555999755859s
Performance | Total latancy measurement for The European Library Open Dataset took 15.986944198608398s
Amount of data | Number of triples check for The European Library Open Dataset took 65.05113101005554s
Interoperability | New terms check for The European Library Open Dataset took 63.269001722335815s
Versatility | Languages check for The European Library Open Dataset took 3.165593147277832s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 3.1694443225860596s
Interpretability | RDF structures check for The European Library Open Dataset took 3.2036001682281494s
Versatility | Serialization formats check for The European Library Open Dataset took 3.19706654548645s
Availability | RDF dump link check for The European Library Open Dataset took 3.1983802318573s
License | MR license check for The European Library Open Dataset took 3.2042016983032227s
License | HR license check for The European Library Open Dataset took 3.197922706604004s
Amount of data | Number of property check for The European Library Open Dataset took 3.2008371353149414s
Understandability | Number of label check for The European Library Open Dataset took 3.744251251220703s
Understandability | URI regex check for The European Library Open Dataset took 6.39661979675293s
Understandability | Vocabs check for The European Library Open Dataset took 3.2037580013275146s
Verifiability | Authors check for The European Library Open Dataset took 3.2000133991241455s
Verifiability | Publishers check for The European Library Open Dataset took 3.198598623275757s
Performance | Throughput check for The European Library Open Dataset took 31.996235370635986s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.128715515136719e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 3.203110694885254s
Interlinking | sameAs chians check for The European Library Open Dataset took 3.3304030895233154s
Interlinking | skos check for The European Library Open Dataset took 3.2482223510742188s
Interlinking | skos check for The European Library Open Dataset took 3.2260334491729736s
Timeliness | dataset update frequency check for The European Library Open Dataset took 3.1856689453125s
Currency | Creation date check for The European Library Open Dataset took 6.370352268218994s
Currency | Modification date check for The European Library Open Dataset took 6.398677587509155s
Rep.Conc. | URIs length for The European Library Open Dataset took 122.85344290733337s
Interoperability | New vocabularies check for The European Library Open Dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 3.193958044052124s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 3.465550422668457s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.026118993759155273s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02745985984802246s
Consistency | Disjoint class check for The European Library Open Dataset took 3.196075916290283s
Consistency | Check Misplaced properties for The European Library Open Dataset took 67.64454531669617s
Consistency | Misplaced classes for The European Library Open Dataset took 3.2606582641601562s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 4.634222984313965s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.1165482997894287s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 64.41108894348145s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.031842708587646484s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 3.191023588180542s
Security | Sign check for The European Library Open Dataset took 3.1994335651397705s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 15.07995867729187s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.37514519691467285s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.021002531051635742s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.031990051269531e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 1.2636184692382812e-05s
INFO | --- Analysis for the-european-library-open-dataset took 912.9174988269806s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 0.7231109142303467s
Availability | VoID file availability check for The Eurostat Linked Data took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.2711808681488037s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.021213293075561523s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 9.72747802734375e-05s
Believability | Calculation of trust value for The Eurostat Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for the-eurostat-linked-data took 6.255811929702759s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 8.821487426757812e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.32580137252807617s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.02153635025024414s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0009827613830566406s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 9.632110595703125e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 1.1920928955078125e-05s
INFO | --- Analysis for the-living-lod-cloud took 44.308637380599976s
Availability | SPARQL endpoint availability check for The View From took 0.056710243225097656s
Availability | VoID file availability check for The View From took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for The View From took 0.27179694175720215s
Reputation | Calculation of the PageRank for The View From took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for The View From took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for The View From took 8.106231689453125e-05s
Believability | Calculation of trust value for The View From took 1.2159347534179688e-05s
INFO | --- Analysis for the-view-from took 2.4781885147094727s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.378908157348633s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.2666621208190918s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.02096390724182129s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 4.00543212890625e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.0967254638671875e-05s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 72.91641211509705s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.192383289337158s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.2650434970855713s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020968914031982422s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 2.86102294921875e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.2159347534179688e-05s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 102.93661713600159s
Availability | SPARQL endpoint availability check for The Content Wrangler took 8.702278137207031e-05s
Availability | VoID file availability check for The Content Wrangler took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.27718567848205566s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.020786762237548828s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00011277198791503906s
Believability | Calculation of trust value for The Content Wrangler took 1.1920928955078125e-05s
INFO | --- Analysis for thecontentwrangler-com took 2.9178805351257324s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 8.606910705566406e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.26512956619262695s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.021255970001220703s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.24249267578125e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 1.2159347534179688e-05s
INFO | --- Analysis for thesaurus-datenwissen took 2.5944221019744873s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.48978161811828613s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.26163554191589355s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.023374557495117188s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.772445678710938e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 1.1444091796875e-05s
INFO | --- Analysis for thesaurus-w took 3.6837236881256104s
Availability | SPARQL endpoint availability check for theses.fr took 8.320808410644531e-05s
Availability | VoID file availability check for theses.fr took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for theses.fr took 0.2641458511352539s
Reputation | Calculation of the PageRank for theses.fr took 0.020726919174194336s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for theses.fr took 5.078315734863281e-05s
Believability | Calculation of trust value for theses.fr took 1.1682510375976562e-05s
INFO | --- Analysis for thesesfr took 4.059371709823608s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 8.535385131835938e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.26483893394470215s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.020908355712890625s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.5762786865234375e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.0251998901367188e-05s
INFO | --- Analysis for Thinkphile took 2.4167656898498535s
Availability | SPARQL endpoint availability check for ThIST took 264.5971326828003s
Availability | VoID file availability check for ThIST took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for ThIST took 0.27353358268737793s
Reputation | Calculation of the PageRank for ThIST took 0.02137589454650879s
Interlinking | Calculation of Degree of Connection for ThIST took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for ThIST took 8.940696716308594e-05s
Believability | Calculation of trust value for ThIST took 1.0728836059570312e-05s
INFO | --- Analysis for thist took 564.3618621826172s
Availability | SPARQL endpoint availability check for TIP took 40.029792070388794s
Availability | VoID file availability check for TIP took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for TIP took 0.29865431785583496s
Reputation | Calculation of the PageRank for TIP took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for TIP took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00010919570922851562s
Believability | Calculation of trust value for TIP took 1.1682510375976562e-05s
INFO | --- Analysis for tip took 102.74240016937256s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 4.124641418457031e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.27486658096313477s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.021120309829711914s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.5762786865234375e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 1.2636184692382812e-05s
INFO | --- Analysis for TOPMODEL took 23.351848125457764s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.556267499923706s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.26940464973449707s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.02115654945373535s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.5762786865234375e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 1.049041748046875e-05s
INFO | --- Analysis for TP-data took 7.417618989944458s
Availability | SPARQL endpoint availability check for Trackloaded Artist Profiles took 2.6117746829986572s
Availability | VoID file availability check for Trackloaded Artist Profiles took 0.0005421638488769531s
Extra | Recovery of all triples for Trackloaded Artist Profiles took 6.626672267913818s
Performance | Total latancy measurement for Trackloaded Artist Profiles took 20.799841165542603s
Amount of data | Number of triples check for Trackloaded Artist Profiles took 6.514929294586182s
Interoperability | New terms check for Trackloaded Artist Profiles took 12.056131839752197s
Versatility | Languages check for Trackloaded Artist Profiles took 7.625237703323364s
Interpretability | Number of blank nodes check for Trackloaded Artist Profiles took 6.711802005767822s
Interpretability | RDF structures check for Trackloaded Artist Profiles took 2.4972128868103027s
Versatility | Serialization formats check for Trackloaded Artist Profiles took 1.8982875347137451s
Availability | RDF dump link check for Trackloaded Artist Profiles took 2.120864152908325s
License | MR license check for Trackloaded Artist Profiles took 2.0726335048675537s
License | HR license check for Trackloaded Artist Profiles took 1.809067964553833s
Amount of data | Number of property check for Trackloaded Artist Profiles took 1.172135829925537s
Understandability | Number of label check for Trackloaded Artist Profiles took 1.334625005722046s
Understandability | URI regex check for Trackloaded Artist Profiles took 3.088618040084839s
Understandability | Vocabs check for Trackloaded Artist Profiles took 2.0091724395751953s
Verifiability | Authors check for Trackloaded Artist Profiles took 1.775024175643921s
Verifiability | Publishers check for Trackloaded Artist Profiles took 2.200141429901123s
Performance | Throughput check for Trackloaded Artist Profiles took 29.793193578720093s
Amount of data | Check the number of entities for Trackloaded Artist Profiles took 7.104873657226562e-05s
Verifiability | Contribs. check for Trackloaded Artist Profiles took 1.3546981811523438s
Interlinking | sameAs chians check for Trackloaded Artist Profiles took 1.0313212871551514s
Interlinking | skos check for Trackloaded Artist Profiles took 1.156742811203003s
Interlinking | skos check for Trackloaded Artist Profiles took 1.3224937915802002s
Timeliness | dataset update frequency check for Trackloaded Artist Profiles took 2.3848700523376465s
Currency | Creation date check for Trackloaded Artist Profiles took 2.3185107707977295s
Currency | Modification date check for Trackloaded Artist Profiles took 2.185633659362793s
Rep.Conc. | URIs length for Trackloaded Artist Profiles took 3.9566571712493896s
Interoperability | New vocabularies check for Trackloaded Artist Profiles took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Trackloaded Artist Profiles took 8.202696800231934s
Consistency | Disjoint class check for Trackloaded Artist Profiles took 1.257758617401123s
Consistency | Check Misplaced properties for Trackloaded Artist Profiles took 2.103973150253296s
Consistency | Misplaced classes for Trackloaded Artist Profiles took 1.1675608158111572s
Consistency | Check Ontology hijacking for Trackloaded Artist Profiles took 2.576744794845581s
Consistency | Check Invalid usage of undefined classes for Trackloaded Artist Profiles took 1.128422737121582s
Consistency | Check Invalid usage of undefined properties for Trackloaded Artist Profiles took 2.177086114883423s
Conciseness | Check Extensional conciseness for Trackloaded Artist Profiles took 0.00013518333435058594s
Security | Sign check for Trackloaded Artist Profiles took 1.4144058227539062s
Availability | Check URIs Dereferenciability for Trackloaded Artist Profiles took 0.8857662677764893s
Completeness | Calculation of interlinking completeness for Trackloaded Artist Profiles took 0.27750110626220703s
Reputation | Calculation of the PageRank for Trackloaded Artist Profiles took 0.021252870559692383s
Interlinking | Calculation of Degree of Connection for Trackloaded Artist Profiles took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Trackloaded Artist Profiles took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Trackloaded Artist Profiles took 1.71661376953125e-05s
Interoperability | Check the re-using of existing vocabs for Trackloaded Artist Profiles took 1.430511474609375e-06s
Believability | Calculation of trust value for Trackloaded Artist Profiles took 2.8133392333984375e-05s
INFO | --- Analysis for trackloaded took 209.02434277534485s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.3302910327911377s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.2687673568725586s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.021498918533325195s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.9114227294921875e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for traditional-korean-medicine took 3.500887155532837s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.20136785507202148s
Availability | VoID file availability check for Traffic Scotland took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.2675290107727051s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.021045684814453125s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.528594970703125e-05s
Believability | Calculation of trust value for Traffic Scotland took 8.58306884765625e-06s
INFO | --- Analysis for traffic-scotland took 2.692945718765259s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.09577465057373047s
Availability | VoID file availability check for Transparency International Linked Data took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.27694177627563477s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.022758960723876953s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010275840759277344s
Believability | Calculation of trust value for Transparency International Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for transparency-linked-data took 2.566915988922119s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.5613079071044922s
Availability | VoID file availability check for transport.data.gov.uk took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.297177791595459s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020724773406982422s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 8.893013000488281e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 8.344650268554688e-06s
INFO | --- Analysis for transport-data-gov-uk took 3.8237712383270264s
Availability | SPARQL endpoint availability check for Trelios took 8.654594421386719e-05s
Availability | VoID file availability check for Trelios took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Trelios took 0.2745494842529297s
Reputation | Calculation of the PageRank for Trelios took 0.021423816680908203s
Interlinking | Calculation of Degree of Connection for Trelios took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.3113021850585938e-05s
Believability | Calculation of trust value for Trelios took 1.1920928955078125e-05s
INFO | --- Analysis for Trelios took 2.4164624214172363s
Availability | SPARQL endpoint availability check for Twarql took 10.545728921890259s
Availability | VoID file availability check for Twarql took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Twarql took 0.268479585647583s
Reputation | Calculation of the PageRank for Twarql took 0.020929336547851562s
Interlinking | Calculation of Degree of Connection for Twarql took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Twarql took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.341934204101562e-05s
Believability | Calculation of trust value for Twarql took 1.2159347534179688e-05s
INFO | --- Analysis for twarql took 12.993221521377563s
Availability | SPARQL endpoint availability check for TWC Data-gov took 8.845329284667969e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.26204419136047363s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.020833253860473633s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.62396240234375e-05s
Believability | Calculation of trust value for TWC Data-gov took 5.245208740234375e-06s
INFO | --- Analysis for twc-data-gov took 12.799690961837769s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.1366569995880127s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.27098774909973145s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.021500825881958008s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 2.9087066650390625e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 8.344650268554688e-06s
INFO | --- Analysis for twc-healthdata took 14.005504369735718s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.0646421909332275s
Availability | VoID file availability check for Instance Hub (all) took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.2724449634552002s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 7.009506225585938e-05s
Believability | Calculation of trust value for Instance Hub (all) took 1.1920928955078125e-05s
INFO | --- Analysis for twc-hub took 74.27835726737976s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.12309098243713379s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.32334351539611816s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.021039724349975586s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0009400844573974609s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00012993812561035156s
Believability | Calculation of trust value for IEEE VIS Source Data took 1.1682510375976562e-05s
INFO | --- Analysis for twc-ieeevis took 99.89510130882263s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 5.435943603515625e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.27849841117858887s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.022723674774169922s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 8.606910705566406e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 8.344650268554688e-06s
INFO | --- Analysis for twc-logd took 2.5630061626434326s
Availability | SPARQL endpoint availability check for twc-opendap took 0.11912202835083008s
Availability | VoID file availability check for twc-opendap took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.267916202545166s
Reputation | Calculation of the PageRank for twc-opendap took 0.0209197998046875s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0009872913360595703s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 8.654594421386719e-05s
Believability | Calculation of trust value for twc-opendap took 1.1920928955078125e-05s
INFO | --- Analysis for twc-opendap took 49.76875424385071s
Availability | SPARQL endpoint availability check for typepad took 4.649162292480469e-05s
Availability | VoID file availability check for typepad took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for typepad took 0.2668585777282715s
Reputation | Calculation of the PageRank for typepad took 0.020947694778442383s
Interlinking | Calculation of Degree of Connection for typepad took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for typepad took 5.14984130859375e-05s
Believability | Calculation of trust value for typepad took 1.3113021850585938e-05s
INFO | --- Analysis for typepad took 2.9970853328704834s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.829287052154541s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.28870439529418945s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.022462844848632812s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.076957702636719e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.0967254638671875e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 4.558576822280884s
Availability | SPARQL endpoint availability check for Uberblic.org took 2.7988686561584473s
Availability | VoID file availability check for Uberblic.org took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.26569604873657227s
Reputation | Calculation of the PageRank for Uberblic.org took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.000102996826171875s
Believability | Calculation of trust value for Uberblic.org took 1.2636184692382812e-05s
INFO | --- Analysis for uberblic took 7.482555627822876s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.548224925994873s
Availability | VoID file availability check for UDante in LiLa took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.2773137092590332s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.02326345443725586s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0009343624114990234s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 4.291534423828125e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for UDante took 4.156919002532959s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 0.8955402374267578s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.26549220085144043s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.020962953567504883s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0009677410125732422s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 4.839897155761719e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for ufo took 4.444018840789795s
Availability | SPARQL endpoint availability check for Uganda Disasters took 8.797645568847656e-05s
Availability | VoID file availability check for Uganda Disasters took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.2650313377380371s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.021429061889648438s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 4.5299530029296875e-05s
Believability | Calculation of trust value for Uganda Disasters took 1.2159347534179688e-05s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.5104658603668213s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.05640673637390137s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0004062652587890625s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.286898136138916s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.0236968994140625s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.0001068115234375s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for uis-linked-data took 2.532899856567383s
Availability | SPARQL endpoint availability check for UK Legislation took 8.225440979003906e-05s
Availability | VoID file availability check for UK Legislation took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.26671671867370605s
Reputation | Calculation of the PageRank for UK Legislation took 0.021072864532470703s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.96453857421875e-05s
Believability | Calculation of trust value for UK Legislation took 9.298324584960938e-06s
INFO | --- Analysis for uk-legislation-api took 3.368243455886841s
Availability | SPARQL endpoint availability check for UK Postcodes took 0.0001392364501953125s
Availability | VoID file availability check for UK Postcodes took 0.00067138671875s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.28148365020751953s
Reputation | Calculation of the PageRank for UK Postcodes took 0.02070903778076172s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.53131103515625e-05s
Believability | Calculation of trust value for UK Postcodes took 1.1920928955078125e-05s
INFO | --- Analysis for uk-postcodes took 22.429183959960938s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 4.1484832763671875e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.27097511291503906s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.021335840225219727s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00012230873107910156s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.1682510375976562e-05s
INFO | --- Analysis for umbel took 6.961989641189575s
Availability | SPARQL endpoint availability check for German environmental thesaurus UMTHES took 4.220008850097656e-05s
Availability | VoID file availability check for German environmental thesaurus UMTHES took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for German environmental thesaurus UMTHES took 0.265155553817749s
Reputation | Calculation of the PageRank for German environmental thesaurus UMTHES took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for German environmental thesaurus UMTHES took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for German environmental thesaurus UMTHES took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for German environmental thesaurus UMTHES took 4.363059997558594e-05s
Believability | Calculation of trust value for German environmental thesaurus UMTHES took 1.0728836059570312e-05s
INFO | --- Analysis for umthes took 3.4039928913116455s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 1.4551477432250977s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.2777135372161865s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.02306199073791504s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0009095668792724609s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.719329833984375e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 5.245208740234375e-06s
INFO | --- Analysis for un-hazardous-numbers took 9.379132509231567s
Availability | SPARQL endpoint availability check for UniProt took 4.190639972686768s
Availability | VoID file availability check for UniProt took 0.0006151199340820312s
Extra | Recovery of all triples for UniProt took 16.01316547393799s
Performance | Total latancy measurement for UniProt took 7.294551849365234s
Amount of data | Number of triples check for UniProt took 0.5638659000396729s
Interoperability | New terms check for UniProt took 1.619497299194336s
Versatility | Languages check for UniProt took 2.578409433364868s
Interpretability | Number of blank nodes check for UniProt took 3.390028953552246s
Interpretability | RDF structures check for UniProt took 1.5964727401733398s
Versatility | Serialization formats check for UniProt took 2.1938834190368652s
Availability | RDF dump link check for UniProt took 0.4715113639831543s
License | MR license check for UniProt took 1.216130256652832s
License | HR license check for UniProt took 300.10375118255615s
Amount of data | Number of property check for UniProt took 0.08254122734069824s
Understandability | Number of label check for UniProt took 46.2276177406311s
Understandability | URI regex check for UniProt took 1.0807063579559326s
Understandability | Vocabs check for UniProt took 0.7507069110870361s
Verifiability | Authors check for UniProt took 1.5289301872253418s
Verifiability | Publishers check for UniProt took 1.389847755432129s
Performance | Throughput check for UniProt took 37.495219230651855s
Amount of data | Check the number of entities for UniProt took 6.890296936035156e-05s
Verifiability | Contribs. check for UniProt took 0.693159818649292s
Interlinking | sameAs chians check for UniProt took 0.6559011936187744s
Interlinking | skos check for UniProt took 1.2536969184875488s
Interlinking | skos check for UniProt took 0.07540369033813477s
Timeliness | dataset update frequency check for UniProt took 1.557732105255127s
Currency | Creation date check for UniProt took 1.8805577754974365s
Currency | Modification date check for UniProt took 1.5859098434448242s
Rep.Conc. | URIs length for UniProt took 123.71275353431702s
Interoperability | New vocabularies check for UniProt took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for UniProt took 0.3711059093475342s
Accuracy | Check Functional Property for UniProt took 0.46764111518859863s
Accuracy | Check Inverse Functional Property for UniProt took 0.3494272232055664s
Accuracy | Check Empty annotation labels for UniProt took 10.640124320983887s
Accuracy | Check White space in annotation for UniProt took 2.5176992416381836s
Accuracy | Check Datatype consistency for UniProt took 7.220084190368652s
Consistency | Disjoint class check for UniProt took 0.35776710510253906s
Consistency | Check Misplaced properties for UniProt took 2.3442301750183105s
Consistency | Check Ontology hijacking for UniProt took 7.877298593521118s
Consistency | Check Invalid usage of undefined classes for UniProt took 18723.18877196312s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.9839801788330078s
Conciseness | Check Extensional conciseness for UniProt took 2.637279510498047s
Conciseness | Check Intensional conciseness for UniProt took 0.7450015544891357s
Security | Sign check for UniProt took 1.1858031749725342s
Availability | Check URIs Dereferenciability for UniProt took 4.148092031478882s
Completeness | Calculation of interlinking completeness for UniProt took 0.6312460899353027s
Reputation | Calculation of the PageRank for UniProt took 0.020876169204711914s
Interlinking | Calculation of Degree of Connection for UniProt took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for UniProt took 4.601478576660156e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 1.9073486328125e-06s
Believability | Calculation of trust value for UniProt took 1.0251998901367188e-05s
INFO | --- Analysis for UniProt took 19746.159754753113s
Availability | SPARQL endpoint availability check for UniProt took 3.8455605506896973s
Availability | VoID file availability check for UniProt took 0.0005762577056884766s
Extra | Recovery of all triples for UniProt took 22.954221963882446s
Performance | Total latancy measurement for UniProt took 7.575918436050415s
Amount of data | Number of triples check for UniProt took 0.5665044784545898s
Versatility | Languages check for UniProt took 2.629197835922241s
Interpretability | Number of blank nodes check for UniProt took 3.303450584411621s
Security | Check HTTPS for UniProt took 3.5078623294830322s
Interpretability | RDF structures check for UniProt took 0.15891289710998535s
Versatility | Serialization formats check for UniProt took 0.16011476516723633s
Availability | RDF dump link check for UniProt took 0.153120756149292s
License | MR license check for UniProt took 0.17016267776489258s
License | HR license check for UniProt took 0.1567237377166748s
Amount of data | Number of property check for UniProt took 0.16486096382141113s
Understandability | Number of label check for UniProt took 0.1796865463256836s
Understandability | URI regex check for UniProt took 0.30736517906188965s
Understandability | Vocabs check for UniProt took 0.15619492530822754s
Verifiability | Authors check for UniProt took 0.15747904777526855s
Verifiability | Publishers check for UniProt took 0.15528178215026855s
Performance | Throughput check for UniProt took 39.84084749221802s
Amount of data | Check the number of entities for UniProt took 0.00014591217041015625s
Verifiability | Contribs. check for UniProt took 0.20008111000061035s
Interlinking | sameAs chians check for UniProt took 0.15678834915161133s
Interlinking | skos check for UniProt took 0.1578810214996338s
Interlinking | skos check for UniProt took 0.12494659423828125s
Timeliness | dataset update frequency check for UniProt took 0.15833044052124023s
Currency | Creation date check for UniProt took 0.3154020309448242s
Currency | Modification date check for UniProt took 0.3152916431427002s
Rep.Conc. | URIs length for UniProt took 116.42554211616516s
Interoperability | New vocabularies check for UniProt took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.16488909721374512s
Accuracy | Check Datatype consistency for UniProt took 7.153372764587402s
Consistency | Disjoint class check for UniProt took 0.1544327735900879s
Consistency | Check Ontology hijacking for UniProt took 0.15712308883666992s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.776374101638794s
Conciseness | Check Extensional conciseness for UniProt took 2.6893186569213867s
Security | Sign check for UniProt took 0.15430545806884766s
Availability | Check URIs Dereferenciability for UniProt took 3.82631778717041s
Completeness | Calculation of interlinking completeness for UniProt took 0.3639521598815918s
Reputation | Calculation of the PageRank for UniProt took 0.020955324172973633s
Interlinking | Calculation of Degree of Connection for UniProt took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for UniProt took 6.556510925292969e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 1.430511474609375e-06s
Believability | Calculation of trust value for UniProt took 1.239776611328125e-05s
INFO | --- Analysis for uniprot took 762.2372131347656s
Availability | SPARQL endpoint availability check for uniprot-metadata took 8.940696716308594e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.26764893531799316s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.021378517150878906s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.365776062011719e-05s
Believability | Calculation of trust value for uniprot-metadata took 1.1205673217773438e-05s
INFO | --- Analysis for uniprot-metadata took 3.6962480545043945s
Availability | SPARQL endpoint availability check for UniProtKB took 3.578585624694824s
Availability | VoID file availability check for UniProtKB took 0.0005307197570800781s
Extra | Recovery of all triples for UniProtKB took 16.703624725341797s
Performance | Total latancy measurement for UniProtKB took 7.254040479660034s
Amount of data | Number of triples check for UniProtKB took 0.4196794033050537s
Interoperability | New terms check for UniProtKB took 1.7551186084747314s
Versatility | Languages check for UniProtKB took 2.171663761138916s
Interpretability | Number of blank nodes check for UniProtKB took 3.295748710632324s
Interpretability | RDF structures check for UniProtKB took 1.6004319190979004s
Versatility | Serialization formats check for UniProtKB took 2.339669704437256s
Availability | RDF dump link check for UniProtKB took 0.2910010814666748s
License | MR license check for UniProtKB took 1.2129602432250977s
License | HR license check for UniProtKB took 300.1062970161438s
Amount of data | Number of property check for UniProtKB took 0.13698816299438477s
Understandability | Number of label check for UniProtKB took 48.98058271408081s
Understandability | URI regex check for UniProtKB took 0.8854076862335205s
Understandability | Vocabs check for UniProtKB took 1.02555513381958s
Verifiability | Authors check for UniProtKB took 1.5123748779296875s
Verifiability | Publishers check for UniProtKB took 1.3053102493286133s
Performance | Throughput check for UniProtKB took 36.97353172302246s
Amount of data | Check the number of entities for UniProtKB took 7.152557373046875e-05s
Verifiability | Contribs. check for UniProtKB took 0.6921229362487793s
Interlinking | sameAs chians check for UniProtKB took 0.6671125888824463s
Interlinking | skos check for UniProtKB took 1.2363407611846924s
Interlinking | skos check for UniProtKB took 0.07726621627807617s
Timeliness | dataset update frequency check for UniProtKB took 1.420079231262207s
Currency | Creation date check for UniProtKB took 1.4726872444152832s
Currency | Modification date check for UniProtKB took 1.8586459159851074s
Rep.Conc. | URIs length for UniProtKB took 115.53096413612366s
Interoperability | New vocabularies check for UniProtKB took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.3761165142059326s
Accuracy | Check Functional Property for UniProtKB took 0.34464192390441895s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.3918113708496094s
Accuracy | Check Empty annotation labels for UniProtKB took 18.193522214889526s
Accuracy | Check White space in annotation for UniProtKB took 2.48508620262146s
Accuracy | Check Datatype consistency for UniProtKB took 7.2473297119140625s
Consistency | Disjoint class check for UniProtKB took 0.34362173080444336s
Consistency | Check Misplaced properties for UniProtKB took 2.151028871536255s
Consistency | Check Ontology hijacking for UniProtKB took 8.378081798553467s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 19639.287489891052s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 1.8698184490203857s
Conciseness | Check Extensional conciseness for UniProtKB took 2.6634020805358887s
Conciseness | Check Intensional conciseness for UniProtKB took 0.7654495239257812s
Security | Sign check for UniProtKB took 1.1282250881195068s
Availability | Check URIs Dereferenciability for UniProtKB took 4.137909889221191s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.6953802108764648s
Reputation | Calculation of the PageRank for UniProtKB took 0.021680116653442383s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 7.05718994140625e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 2.1457672119140625e-06s
Believability | Calculation of trust value for UniProtKB took 1.049041748046875e-05s
INFO | --- Analysis for uniprotkb took 20748.777282476425s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.2770514488220215s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.020928621292114258s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 3.5343072414398193s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 8.296966552734375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.2693665027618408s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.021144390106201172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 3.827761650085449s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 8.511543273925781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.2963864803314209s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.021500110626220703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 3.429457426071167s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.2676260471343994s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.020966529846191406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-basque took 3.3296194076538086s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.2793281078338623s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.02104926109313965s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 3.3538193702697754s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 8.606910705566406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.27390265464782715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.022726774215698242s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 5.0067901611328125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 3.397554636001587s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.2614562511444092s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.02153182029724121s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 3.945146083831787s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 9.202957153320312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.2775111198425293s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.021068811416625977s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 3.4770588874816895s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 8.368492126464844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.26874828338623047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.021222829818725586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 3.4322428703308105s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 8.7738037109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.2687997817993164s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.02084970474243164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 3.406397581100464s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.2646291255950928s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.020987272262573242s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 3.2540478706359863s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 4.5299530029296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.2772989273071289s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 3.234884738922119s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 8.440017700195312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.27156615257263184s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-danish took 4.036951541900635s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.673004150390625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.2777395248413086s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.02174210548400879s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0008187294006347656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 3.588594436645508s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.00011372566223144531s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.2942631244659424s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.022900104522705078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 3.2611401081085205s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 8.416175842285156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0009992122650146484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.2672443389892578s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.020602941513061523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-english took 3.3252639770507812s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 8.535385131835938e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.2856428623199463s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.021123170852661133s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 3.1970162391662598s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 0.00010061264038085938s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.276364803314209s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.0221250057220459s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 3.28989839553833s
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.0006585121154785156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.27503466606140137s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.021451473236083984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 3.294454336166382s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 8.392333984375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.2743532657623291s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020946741104125977s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 3.915426015853882s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 5.888938903808594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.26889681816101074s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.02096414566040039s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 3.2348508834838867s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 8.726119995117188e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.2647218704223633s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.02057790756225586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-french took 3.34563946723938s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 8.678436279296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.27658939361572266s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.0217435359954834s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 4.744529724121094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician took 3.404848098754883s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.28957200050354004s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.020880937576293945s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 4.601478576660156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 3.6168341636657715s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 8.440017700195312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.2647440433502197s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-german took 3.858867645263672s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.281008243560791s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.021922588348388672s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 3.695487976074219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 3.8367397785186768s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 8.440017700195312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.26497769355773926s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.020946502685546875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0009174346923828125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 4.601478576660156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-greek took 3.7257771492004395s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 8.559226989746094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.27704310417175293s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.021646499633789062s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 3.4296481609344482s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 8.249282836914062e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.27720117568969727s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.02117776870727539s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 3.397531032562256s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 6.031990051269531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.32957005500793457s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.020884990692138672s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.000957489013671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 4.7206878662109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 3.802399158477783s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.3068985939025879s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.0212404727935791s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 3.5594847202301025s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 0.00010466575622558594s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.26256394386291504s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.0211336612701416s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-irish took 3.719688892364502s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.26678037643432617s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.020992755889892578s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-italian took 4.046221017837524s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.2659730911254883s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.024965286254882812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.001317739486694336s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 5.435943603515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 4.362366676330566s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 0.00010657310485839844s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.2666609287261963s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.02091383934020996s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 3.560711145401001s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 4.553794860839844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.29486727714538574s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.023439645767211914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 3.3281545639038086s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 8.368492126464844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.2740600109100342s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.02253246307373047s
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.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin took 3.8017141819000244s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.2631568908691406s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.022016286849975586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 3.1746785640716553s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.2737233638763428s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.020360231399536133s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 3.271402597427368s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.26718688011169434s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.02081918716430664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 3.437220811843872s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 9.083747863769531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.26262664794921875s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.02248239517211914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 4.673004150390625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 3.1499485969543457s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.27318382263183594s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.022733211517333984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 3.3676438331604004s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 9.822845458984375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.001271963119506836s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.2762477397918701s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.021008968353271484s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-persian took 3.8288381099700928s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.27773261070251465s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.02179241180419922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-polish took 3.388028144836426s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 8.463859558105469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.2651379108428955s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.02061152458190918s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 2.9358317852020264s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 8.606910705566406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.2644989490509033s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020671367645263672s
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.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 3.223768711090088s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 8.58306884765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.28223705291748047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.021715879440307617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 3.3989124298095703s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.2719740867614746s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 3.346625804901123s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 0.00010275840759277344s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.29259824752807617s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.023328781127929688s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian took 3.3564817905426025s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0003056526184082031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.2742602825164795s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 3.4848482608795166s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.27709078788757324s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.020907163619995117s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 3.3631837368011475s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0003719329833984375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.28169703483581543s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.0207061767578125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 3.3852336406707764s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 5.0067901611328125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0002982616424560547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.2575702667236328s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 3.1830852031707764s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.00029969215393066406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.25919342041015625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.020305156707763672s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 3.1036057472229004s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0003044605255126953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.26602768898010254s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 3.232811212539673s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0011410713195800781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.26622486114501953s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.02089667320251465s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 3.1668455600738525s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.00034928321838378906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.26268506050109863s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.021404266357421875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 3.647824287414551s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 8.535385131835938e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.2725644111633301s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.021193742752075195s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 3.749234199523926s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 8.797645568847656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.3457059860229492s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.021666288375854492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 3.573681116104126s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 0.00011181831359863281s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.29378557205200195s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 3.403965473175049s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.2623012065887451s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.021491289138793945s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 3.3302829265594482s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.2711629867553711s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.022043943405151367s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 3.730545997619629s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.2763705253601074s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.020659923553466797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 3.4285247325897217s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.2653050422668457s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.02129817008972168s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0008172988891601562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 3.298968553543091s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 8.487701416015625e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.288785457611084s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.604194641113281e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 1.1205673217773438e-05s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 6.558952331542969s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 4.172325134277344e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.2634282112121582s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 4.839897155761719e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.1920928955078125e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 2.958526611328125s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 4.1484832763671875e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.2674143314361572s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.2901763916015625e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 9.5367431640625e-06s
INFO | --- Analysis for university-sussex-reading-lists took 2.6907496452331543s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 6.612740755081177s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.28688716888427734s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.020703792572021484s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 6.961822509765625e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 1.0728836059570312e-05s
INFO | --- Analysis for unodc took 17.187734365463257s
Availability | SPARQL endpoint availability check for Super Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Super Ontology took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.2726123332977295s
Reputation | Calculation of the PageRank for Super Ontology took 0.02051568031311035s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 7.915496826171875e-05s
Believability | Calculation of trust value for Super Ontology took 9.775161743164062e-06s
INFO | --- Analysis for upper-ontology took 3.29785418510437s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 1.2678208351135254s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.27045106887817383s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.020812511444091797s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0010173320770263672s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 4.124641418457031e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 1.1444091796875e-05s
INFO | --- Analysis for Upper_Ontology took 5.574726343154907s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 8.630752563476562e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.0010819435119628906s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.2717018127441406s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 3.0040740966796875e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 1.1920928955078125e-05s
INFO | --- Analysis for Urban_Atlas_ took 2.4809019565582275s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 0.4949359893798828s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.0002853870391845703s
Extra | Recovery of all triples for Urban Atlas dataset @PSNC took 130.00537514686584s
Performance | Total latancy measurement for Urban Atlas dataset @PSNC took 0.9116437435150146s
Amount of data | Number of triples check for Urban Atlas dataset @PSNC took 9.665634870529175s
Interoperability | New terms check for Urban Atlas dataset @PSNC took 14.133835554122925s
Versatility | Languages check for Urban Atlas dataset @PSNC took 300.1843411922455s
Interpretability | Number of blank nodes check for Urban Atlas dataset @PSNC took 2.0876471996307373s
Interpretability | RDF structures check for Urban Atlas dataset @PSNC took 0.26505446434020996s
Versatility | Serialization formats check for Urban Atlas dataset @PSNC took 8.557696104049683s
Availability | RDF dump link check for Urban Atlas dataset @PSNC took 0.30154967308044434s
License | MR license check for Urban Atlas dataset @PSNC took 0.6168761253356934s
License | HR license check for Urban Atlas dataset @PSNC took 300.21629095077515s
Amount of data | Number of property check for Urban Atlas dataset @PSNC took 0.18292927742004395s
Understandability | Number of label check for Urban Atlas dataset @PSNC took 2.3147435188293457s
Understandability | URI regex check for Urban Atlas dataset @PSNC took 0.8052489757537842s
Understandability | Vocabs check for Urban Atlas dataset @PSNC took 0.3842747211456299s
Verifiability | Authors check for Urban Atlas dataset @PSNC took 0.1835036277770996s
Verifiability | Publishers check for Urban Atlas dataset @PSNC took 0.2320244312286377s
Performance | Throughput check for Urban Atlas dataset @PSNC took 10.943145036697388s
Amount of data | Check the number of entities for Urban Atlas dataset @PSNC took 0.00012803077697753906s
Verifiability | Contribs. check for Urban Atlas dataset @PSNC took 0.18164467811584473s
Interlinking | sameAs chians check for Urban Atlas dataset @PSNC took 0.18389511108398438s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.4837353229522705s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.4320821762084961s
Timeliness | dataset update frequency check for Urban Atlas dataset @PSNC took 5.261490345001221s
Currency | Creation date check for Urban Atlas dataset @PSNC took 0.45246243476867676s
Currency | Modification date check for Urban Atlas dataset @PSNC took 0.23274683952331543s
Rep.Conc. | URIs length for Urban Atlas dataset @PSNC took 161.6235420703888s
Interoperability | New vocabularies check for Urban Atlas dataset @PSNC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Urban Atlas dataset @PSNC took 0.18171310424804688s
Accuracy | Check Functional Property for Urban Atlas dataset @PSNC took 0.31345438957214355s
Accuracy | Check Inverse Functional Property for Urban Atlas dataset @PSNC took 0.31406140327453613s
Accuracy | Check Empty annotation labels for Urban Atlas dataset @PSNC took 43.01709055900574s
Accuracy | Check White space in annotation for Urban Atlas dataset @PSNC took 2.6632015705108643s
Accuracy | Check Datatype consistency for Urban Atlas dataset @PSNC took 2.618198871612549s
Consistency | Disjoint class check for Urban Atlas dataset @PSNC took 0.179520845413208s
Consistency | Check Misplaced properties for Urban Atlas dataset @PSNC took 85.85906314849854s
Consistency | Misplaced classes for Urban Atlas dataset @PSNC took 8.222126483917236s
Consistency | Check Ontology hijacking for Urban Atlas dataset @PSNC took 37.29811954498291s
Consistency | Check Invalid usage of undefined classes for Urban Atlas dataset @PSNC took 1.3889679908752441s
Consistency | Check Invalid usage of undefined properties for Urban Atlas dataset @PSNC took 86.69791436195374s
Conciseness | Check Extensional conciseness for Urban Atlas dataset @PSNC took 2.7009549140930176s
Conciseness | Check Intensional conciseness for Urban Atlas dataset @PSNC took 0.5223948955535889s
Security | Sign check for Urban Atlas dataset @PSNC took 0.6028506755828857s
Availability | Check URIs Dereferenciability for Urban Atlas dataset @PSNC took 10.702327966690063s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.5212147235870361s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.02143239974975586s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for Urban Atlas dataset @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 8.106231689453125e-06s
INFO | --- Analysis for Urban_Atlas_Dataset took 2262.274251461029s
Availability | SPARQL endpoint availability check for URIBurner took 0.933866024017334s
Availability | VoID file availability check for URIBurner took 0.0005848407745361328s
Extra | Recovery of all triples for URIBurner took 120.76914858818054s
Performance | Total latancy measurement for URIBurner took 2.6352720260620117s
Amount of data | Number of triples check for URIBurner took 3.4852023124694824s
Interoperability | New terms check for URIBurner took 37.721067667007446s
Versatility | Languages check for URIBurner took 122.66379952430725s
Interpretability | Number of blank nodes check for URIBurner took 1.8189740180969238s
Security | Check HTTPS for URIBurner took 0.8732633590698242s
Interpretability | RDF structures check for URIBurner took 3.306055784225464s
Versatility | Serialization formats check for URIBurner took 6.557760953903198s
Availability | RDF dump link check for URIBurner took 45.52802920341492s
License | MR license check for URIBurner took 1.1399486064910889s
License | HR license check for URIBurner took 122.33404898643494s
Amount of data | Number of property check for URIBurner took 0.816857099533081s
Understandability | Number of label check for URIBurner took 3.93086314201355s
Understandability | URI regex check for URIBurner took 1.257598876953125s
Understandability | Vocabs check for URIBurner took 0.6208384037017822s
Verifiability | Authors check for URIBurner took 1.709907054901123s
Verifiability | Publishers check for URIBurner took 0.6084966659545898s
Performance | Throughput check for URIBurner took 10.656984567642212s
Amount of data | Check the number of entities for URIBurner took 0.00012922286987304688s
Verifiability | Contribs. check for URIBurner took 0.5802412033081055s
Interlinking | sameAs chians check for URIBurner took 1.2294015884399414s
Interlinking | skos check for URIBurner took 0.7642273902893066s
Interlinking | skos check for URIBurner took 0.5128946304321289s
Timeliness | dataset update frequency check for URIBurner took 0.9642815589904785s
Currency | Creation date check for URIBurner took 3.2285971641540527s
Currency | Modification date check for URIBurner took 0.7405898571014404s
Rep.Conc. | URIs length for URIBurner took 113.02267909049988s
Interoperability | New vocabularies check for URIBurner took 529.2474434375763s
Consistency | Deprecated classes/propertiers check for URIBurner took 0.7134177684783936s
Accuracy | Check Functional Property for URIBurner took 0.601447343826294s
Accuracy | Check Inverse Functional Property for URIBurner took 0.5492024421691895s
Accuracy | Check Empty annotation labels for URIBurner took 56.63411211967468s
Accuracy | Check White space in annotation for URIBurner took 0.1834859848022461s
Consistency | Disjoint class check for URIBurner took 0.601853609085083s
Consistency | Check Misplaced properties for URIBurner took 373.24326062202454s
Consistency | Misplaced classes for URIBurner took 56.74416756629944s
Consistency | Check Ontology hijacking for URIBurner took 58.030250787734985s
Consistency | Check Invalid usage of undefined properties for URIBurner took 58.362605810165405s
Conciseness | Check Extensional conciseness for URIBurner took 0.00017118453979492188s
Conciseness | Check Intensional conciseness for URIBurner took 110.58934235572815s
Security | Sign check for URIBurner took 0.775702953338623s
Completeness | Calculation of interlinking completeness for URIBurner took 0.7594506740570068s
Reputation | Calculation of the PageRank for URIBurner took 0.022704124450683594s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for URIBurner took 9.989738464355469e-05s
Interoperability | Check the re-using of existing vocabs for URIBurner took 24.488435983657837s
Believability | Calculation of trust value for URIBurner took 1.049041748046875e-05s
INFO | --- Analysis for uriburner took 11186.173214197159s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 8.893013000488281e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.2723386287689209s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.021846771240234375s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0010192394256591797s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.695487976074219e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 6.9141387939453125e-06s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 2.6347899436950684s
Availability | SPARQL endpoint availability check for Legija Stranaca took 8.440017700195312e-05s
Availability | VoID file availability check for Legija Stranaca took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.26332616806030273s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.020817041397094727s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 2.9087066650390625e-05s
Believability | Calculation of trust value for Legija Stranaca took 1.239776611328125e-05s
INFO | --- Analysis for Uros_Legija_Susa took 2.463266372680664s
Availability | SPARQL endpoint availability check for Legija took 9.632110595703125e-05s
Availability | VoID file availability check for Legija took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Legija took 0.2697415351867676s
Reputation | Calculation of the PageRank for Legija took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for Legija took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Legija took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Legija took 2.9087066650390625e-05s
Believability | Calculation of trust value for Legija took 1.1682510375976562e-05s
INFO | --- Analysis for Uros_Susa took 2.4224021434783936s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.5277657508850098s
Availability | VoID file availability check for USAGE review corpus took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.2985217571258545s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.021581411361694336s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.0279159545898438e-05s
Believability | Calculation of trust value for USAGE review corpus took 1.1205673217773438e-05s
INFO | --- Analysis for usage-review-corpus took 3.758925199508667s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 5.175612449645996s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.2616147994995117s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.462501525878906e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 1.2636184692382812e-05s
INFO | --- Analysis for utpl-lod took 10.084868431091309s
Availability | SPARQL endpoint availability check for terrorist attack took 4.0531158447265625e-05s
Availability | VoID file availability check for terrorist attack took 0.0006346702575683594s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.2930159568786621s
Reputation | Calculation of the PageRank for terrorist attack took 0.021634340286254883s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 2.9802322387695312e-05s
Believability | Calculation of trust value for terrorist attack took 1.1920928955078125e-05s
INFO | --- Analysis for varsha took 4.135565996170044s
Availability | SPARQL endpoint availability check for VA took 8.344650268554688e-05s
Availability | VoID file availability check for VA took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for VA took 0.2699100971221924s
Reputation | Calculation of the PageRank for VA took 0.020789623260498047s
Interlinking | Calculation of Degree of Connection for VA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VA took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for VA took 2.9802322387695312e-05s
Believability | Calculation of trust value for VA took 8.344650268554688e-06s
INFO | --- Analysis for Vehicule_Autonome took 2.601168394088745s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 0.5212392807006836s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.26796698570251465s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.022960424423217773s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for VelezIndexTotiusArtis took 4.0353052616119385s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 6.468085527420044s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.2615854740142822s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.020774126052856445s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 8.392333984375e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 1.0013580322265625e-05s
INFO | --- Analysis for verrijktkoninkrijk took 14.703770399093628s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 8.559226989746094e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.26722025871276855s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.020650386810302734s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.0001728534698486328s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.1920928955078125e-05s
INFO | --- Analysis for viaf took 21.244728803634644s
Availability | SPARQL endpoint availability check for Vihar Exports took 8.225440979003906e-05s
Availability | VoID file availability check for Vihar Exports took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.2709355354309082s
Reputation | Calculation of the PageRank for Vihar Exports took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 2.9325485229492188e-05s
Believability | Calculation of trust value for Vihar Exports took 8.678436279296875e-05s
INFO | --- Analysis for Vihar_Exports took 2.4143168926239014s
Availability | SPARQL endpoint availability check for VIVO took 8.177757263183594e-05s
Availability | VoID file availability check for VIVO took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for VIVO took 0.2690434455871582s
Reputation | Calculation of the PageRank for VIVO took 0.02115488052368164s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for VIVO took 6.318092346191406e-05s
Believability | Calculation of trust value for VIVO took 1.0251998901367188e-05s
INFO | --- Analysis for vivo took 4.69515585899353s
Availability | SPARQL endpoint availability check for VIVO Cornell took 8.749961853027344e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.26738882064819336s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.021322965621948242s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.0108642578125e-05s
Believability | Calculation of trust value for VIVO Cornell took 9.298324584960938e-06s
INFO | --- Analysis for vivo-cornell-university took 6.035445690155029s
Availability | SPARQL endpoint availability check for VIVO Indiana took 8.296966552734375e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.2804908752441406s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.02355170249938965s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 7.915496826171875e-05s
Believability | Calculation of trust value for VIVO Indiana took 1.0013580322265625e-05s
INFO | --- Analysis for vivo-indiana-university took 3.028252363204956s
Availability | SPARQL endpoint availability check for VIVO Ponce took 8.702278137207031e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.29828977584838867s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.337860107421875e-05s
Believability | Calculation of trust value for VIVO Ponce took 9.5367431640625e-06s
INFO | --- Analysis for vivo-ponce took 2.90083384513855s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 8.392333984375e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.2632477283477783s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.021432876586914062s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0008044242858886719s
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 1.1920928955078125e-05s
INFO | --- Analysis for vivo-scripps-research-institute took 2.8478355407714844s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 8.249282836914062e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.28058433532714844s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.021220684051513672s
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.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.512901306152344e-05s
Believability | Calculation of trust value for VIVO University of Florida took 1.2159347534179688e-05s
INFO | --- Analysis for vivo-university-of-florida took 2.7584261894226074s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 8.487701416015625e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.271892786026001s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.02089214324951172s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.695487976074219e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 1.1444091796875e-05s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 2.8133535385131836s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 8.416175842285156e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.2626664638519287s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.02266526222229004s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 4.220008850097656e-05s
Believability | Calculation of trust value for VIVO WUSTL took 1.0013580322265625e-05s
INFO | --- Analysis for vivo-wustl took 2.8643927574157715s
Availability | SPARQL endpoint availability check for vivo2doi took 8.368492126464844e-05s
Availability | VoID file availability check for vivo2doi took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.2634620666503906s
Reputation | Calculation of the PageRank for vivo2doi took 0.021033763885498047s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 5.7697296142578125e-05s
Believability | Calculation of trust value for vivo2doi took 1.1444091796875e-05s
INFO | --- Analysis for vivo2doi took 25.417542934417725s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 8.320808410644531e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.353107213973999s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.021249055862426758s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.914138793945312e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 1.0728836059570312e-05s
INFO | --- Analysis for vu-wordnet took 14.211156129837036s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.1300041675567627s
Availability | VoID file availability check for vulnerapedia took 0.000244140625s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.26737165451049805s
Reputation | Calculation of the PageRank for vulnerapedia took 0.022226333618164062s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 6.818771362304688e-05s
Believability | Calculation of trust value for vulnerapedia took 1.0728836059570312e-05s
INFO | --- Analysis for vulnerapedia took 2.9714417457580566s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 8.344650268554688e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.26828765869140625s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.02095818519592285s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.1920928955078125e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.1682510375976562e-05s
INFO | --- Analysis for VVASIAK took 2.433987617492676s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 0.00010013580322265625s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.2660644054412842s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.020636320114135742s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.075599670410156e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 1.1444091796875e-05s
INFO | --- Analysis for Vyvasta took 2.462822198867798s
Availability | SPARQL endpoint availability check for W3C took 8.320808410644531e-05s
Availability | VoID file availability check for W3C took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for W3C took 0.27135729789733887s
Reputation | Calculation of the PageRank for W3C took 0.020765304565429688s
Interlinking | Calculation of Degree of Connection for W3C took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for W3C took 0.0001361370086669922s
Believability | Calculation of trust value for W3C took 1.1920928955078125e-05s
INFO | --- Analysis for w3c took 2.7438724040985107s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 9.679794311523438e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.2855491638183594s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.021069765090942383s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00010943412780761719s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 1.0967254638671875e-05s
INFO | --- Analysis for w3c-wordnet took 3.843621015548706s
Availability | SPARQL endpoint availability check for WarSampo took 0.33035731315612793s
Availability | VoID file availability check for WarSampo took 0.00048160552978515625s
Extra | Recovery of all triples for WarSampo took 26.570254802703857s
Performance | Total latancy measurement for WarSampo took 0.7963137626647949s
Amount of data | Number of triples check for WarSampo took 18.448491096496582s
Interoperability | New terms check for WarSampo took 3.909069538116455s
Versatility | Languages check for WarSampo took 54.20543146133423s
Interpretability | Number of blank nodes check for WarSampo took 18.060382843017578s
Security | Check HTTPS for WarSampo took 0.38057494163513184s
Interpretability | RDF structures check for WarSampo took 0.19194483757019043s
Versatility | Serialization formats check for WarSampo took 0.20237350463867188s
Availability | RDF dump link check for WarSampo took 1.1804423332214355s
License | MR license check for WarSampo took 0.1872255802154541s
License | HR license check for WarSampo took 43.81092309951782s
Amount of data | Number of property check for WarSampo took 0.19407296180725098s
Understandability | Number of label check for WarSampo took 9.706249713897705s
Understandability | URI regex check for WarSampo took 0.33704185485839844s
Understandability | Vocabs check for WarSampo took 0.15424346923828125s
Verifiability | Authors check for WarSampo took 0.1995551586151123s
Verifiability | Publishers check for WarSampo took 0.1874401569366455s
Performance | Throughput check for WarSampo took 10.706222772598267s
Amount of data | Check the number of entities for WarSampo took 14.889003038406372s
Verifiability | Contribs. check for WarSampo took 0.20431804656982422s
Interlinking | sameAs chians check for WarSampo took 0.19316864013671875s
Interlinking | skos check for WarSampo took 0.20412755012512207s
Interlinking | skos check for WarSampo took 0.1489887237548828s
Timeliness | dataset update frequency check for WarSampo took 0.1597602367401123s
Currency | Creation date check for WarSampo took 0.3621220588684082s
Currency | Modification date check for WarSampo took 0.3567676544189453s
Rep.Conc. | URIs length for WarSampo took 50.367974042892456s
Interoperability | New vocabularies check for WarSampo took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.19638872146606445s
Accuracy | Check Functional Property for WarSampo took 0.19499874114990234s
Accuracy | Check Inverse Functional Property for WarSampo took 0.15374135971069336s
Accuracy | Check Empty annotation labels for WarSampo took 11.362333297729492s
Accuracy | Check White space in annotation for WarSampo took 2.175095796585083s
Accuracy | Check Datatype consistency for WarSampo took 5.3014678955078125s
Consistency | Disjoint class check for WarSampo took 0.18700003623962402s
Consistency | Check Misplaced properties for WarSampo took 20.52419424057007s
Consistency | Check Ontology hijacking for WarSampo took 18.92052435874939s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.3907546997070312s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.6141822338104248s
Conciseness | Check Extensional conciseness for WarSampo took 2.784667491912842s
Conciseness | Check Intensional conciseness for WarSampo took 0.26171398162841797s
Security | Sign check for WarSampo took 0.1625208854675293s
Availability | Check URIs Dereferenciability for WarSampo took 2.989873170852661s
Completeness | Calculation of interlinking completeness for WarSampo took 0.4985346794128418s
Reputation | Calculation of the PageRank for WarSampo took 0.021381855010986328s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for WarSampo took 8.845329284667969e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 2.6226043701171875e-06s
Believability | Calculation of trust value for WarSampo took 1.0728836059570312e-05s
INFO | --- Analysis for warsampo took 898.2684919834137s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.39108967781067s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0003485679626464844s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.2692694664001465s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.021418094635009766s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 7.939338684082031e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 1.2159347534179688e-05s
INFO | --- Analysis for wasabi took 54.633657693862915s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 0.48629045486450195s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.0004572868347167969s
Extra | Recovery of all triples for FAO water areas classification as linked data @PSNC took 126.38621759414673s
Performance | Total latancy measurement for FAO water areas classification as linked data @PSNC took 0.931757926940918s
Amount of data | Number of triples check for FAO water areas classification as linked data @PSNC took 9.18704342842102s
Interoperability | New terms check for FAO water areas classification as linked data @PSNC took 13.851047277450562s
Versatility | Languages check for FAO water areas classification as linked data @PSNC took 300.17683482170105s
Interpretability | Number of blank nodes check for FAO water areas classification as linked data @PSNC took 2.1737143993377686s
Interpretability | RDF structures check for FAO water areas classification as linked data @PSNC took 0.24747037887573242s
Versatility | Serialization formats check for FAO water areas classification as linked data @PSNC took 11.727565050125122s
Availability | RDF dump link check for FAO water areas classification as linked data @PSNC took 0.30622386932373047s
License | MR license check for FAO water areas classification as linked data @PSNC took 0.7026593685150146s
License | HR license check for FAO water areas classification as linked data @PSNC took 300.20675826072693s
Amount of data | Number of property check for FAO water areas classification as linked data @PSNC took 0.18587541580200195s
Understandability | Number of label check for FAO water areas classification as linked data @PSNC took 2.1272904872894287s
Understandability | URI regex check for FAO water areas classification as linked data @PSNC took 0.7389299869537354s
Understandability | Vocabs check for FAO water areas classification as linked data @PSNC took 0.3463015556335449s
Verifiability | Authors check for FAO water areas classification as linked data @PSNC took 0.17808151245117188s
Verifiability | Publishers check for FAO water areas classification as linked data @PSNC took 0.219099760055542s
Performance | Throughput check for FAO water areas classification as linked data @PSNC took 10.674577474594116s
Amount of data | Check the number of entities for FAO water areas classification as linked data @PSNC took 7.295608520507812e-05s
Verifiability | Contribs. check for FAO water areas classification as linked data @PSNC took 0.17884159088134766s
Interlinking | sameAs chians check for FAO water areas classification as linked data @PSNC took 0.1770172119140625s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.46779370307922363s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.3911454677581787s
Timeliness | dataset update frequency check for FAO water areas classification as linked data @PSNC took 4.970254182815552s
Currency | Creation date check for FAO water areas classification as linked data @PSNC took 0.4339866638183594s
Currency | Modification date check for FAO water areas classification as linked data @PSNC took 0.22942543029785156s
Rep.Conc. | URIs length for FAO water areas classification as linked data @PSNC took 159.39666604995728s
Interoperability | New vocabularies check for FAO water areas classification as linked data @PSNC took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for FAO water areas classification as linked data @PSNC took 0.17739105224609375s
Accuracy | Check Functional Property for FAO water areas classification as linked data @PSNC took 0.22721409797668457s
Accuracy | Check Inverse Functional Property for FAO water areas classification as linked data @PSNC took 0.34218502044677734s
Accuracy | Check Empty annotation labels for FAO water areas classification as linked data @PSNC took 42.91346573829651s
Accuracy | Check White space in annotation for FAO water areas classification as linked data @PSNC took 2.651641845703125s
Accuracy | Check Datatype consistency for FAO water areas classification as linked data @PSNC took 2.612292766571045s
Consistency | Disjoint class check for FAO water areas classification as linked data @PSNC took 0.1874077320098877s
Consistency | Check Misplaced properties for FAO water areas classification as linked data @PSNC took 85.66739201545715s
Consistency | Misplaced classes for FAO water areas classification as linked data @PSNC took 8.241650104522705s
Consistency | Check Ontology hijacking for FAO water areas classification as linked data @PSNC took 37.10180068016052s
Consistency | Check Invalid usage of undefined classes for FAO water areas classification as linked data @PSNC took 1.259122610092163s
Consistency | Check Invalid usage of undefined properties for FAO water areas classification as linked data @PSNC took 86.53024315834045s
Conciseness | Check Extensional conciseness for FAO water areas classification as linked data @PSNC took 2.705270290374756s
Conciseness | Check Intensional conciseness for FAO water areas classification as linked data @PSNC took 0.518477201461792s
Security | Sign check for FAO water areas classification as linked data @PSNC took 0.9629323482513428s
Availability | Check URIs Dereferenciability for FAO water areas classification as linked data @PSNC took 9.046458959579468s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.5003719329833984s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.02197432518005371s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 5.221366882324219e-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.2874603271484375e-05s
INFO | --- Analysis for Water_Areas_Classification took 2257.118590116501s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 0.1779036521911621s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.0005433559417724609s
Extra | Recovery of all triples for Water buffer dataset from Czech Republic @PSNC took 130.9115025997162s
Performance | Total latancy measurement for Water buffer dataset from Czech Republic @PSNC took 0.895733118057251s
Amount of data | Number of triples check for Water buffer dataset from Czech Republic @PSNC took 9.167873859405518s
Interoperability | New terms check for Water buffer dataset from Czech Republic @PSNC took 14.127695083618164s
Versatility | Languages check for Water buffer dataset from Czech Republic @PSNC took 300.2326683998108s
Interpretability | Number of blank nodes check for Water buffer dataset from Czech Republic @PSNC took 1.9431991577148438s
Interpretability | RDF structures check for Water buffer dataset from Czech Republic @PSNC took 0.2671849727630615s
Versatility | Serialization formats check for Water buffer dataset from Czech Republic @PSNC took 9.617145776748657s
Availability | RDF dump link check for Water buffer dataset from Czech Republic @PSNC took 0.2825467586517334s
License | MR license check for Water buffer dataset from Czech Republic @PSNC took 0.6172397136688232s
License | HR license check for Water buffer dataset from Czech Republic @PSNC took 300.2156434059143s
Amount of data | Number of property check for Water buffer dataset from Czech Republic @PSNC took 0.1861429214477539s
Understandability | Number of label check for Water buffer dataset from Czech Republic @PSNC took 1.1967310905456543s
Understandability | URI regex check for Water buffer dataset from Czech Republic @PSNC took 0.6904938220977783s
Understandability | Vocabs check for Water buffer dataset from Czech Republic @PSNC took 0.42380690574645996s
Verifiability | Authors check for Water buffer dataset from Czech Republic @PSNC took 0.18578886985778809s
Verifiability | Publishers check for Water buffer dataset from Czech Republic @PSNC took 0.2261500358581543s
Performance | Throughput check for Water buffer dataset from Czech Republic @PSNC took 10.828660488128662s
Amount of data | Check the number of entities for Water buffer dataset from Czech Republic @PSNC took 0.000152587890625s
Verifiability | Contribs. check for Water buffer dataset from Czech Republic @PSNC took 0.17415547370910645s
Interlinking | sameAs chians check for Water buffer dataset from Czech Republic @PSNC took 0.18651247024536133s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.39811134338378906s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.4107179641723633s
Timeliness | dataset update frequency check for Water buffer dataset from Czech Republic @PSNC took 5.813394546508789s
Currency | Creation date check for Water buffer dataset from Czech Republic @PSNC took 0.4342536926269531s
Currency | Modification date check for Water buffer dataset from Czech Republic @PSNC took 0.223527193069458s
Rep.Conc. | URIs length for Water buffer dataset from Czech Republic @PSNC took 149.87388396263123s
Interoperability | New vocabularies check for Water buffer dataset from Czech Republic @PSNC took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for Water buffer dataset from Czech Republic @PSNC took 0.17840242385864258s
Accuracy | Check Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.26454663276672363s
Accuracy | Check Inverse Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.2715730667114258s
Accuracy | Check Empty annotation labels for Water buffer dataset from Czech Republic @PSNC took 37.83154249191284s
Accuracy | Check White space in annotation for Water buffer dataset from Czech Republic @PSNC took 2.6605048179626465s
Accuracy | Check Datatype consistency for Water buffer dataset from Czech Republic @PSNC took 2.64028000831604s
Consistency | Disjoint class check for Water buffer dataset from Czech Republic @PSNC took 0.1811361312866211s
Consistency | Check Misplaced properties for Water buffer dataset from Czech Republic @PSNC took 86.37257671356201s
Consistency | Misplaced classes for Water buffer dataset from Czech Republic @PSNC took 8.364725828170776s
Consistency | Check Ontology hijacking for Water buffer dataset from Czech Republic @PSNC took 36.427061557769775s
Consistency | Check Invalid usage of undefined classes for Water buffer dataset from Czech Republic @PSNC took 1.2671942710876465s
Consistency | Check Invalid usage of undefined properties for Water buffer dataset from Czech Republic @PSNC took 87.54455900192261s
Conciseness | Check Extensional conciseness for Water buffer dataset from Czech Republic @PSNC took 2.738279104232788s
Conciseness | Check Intensional conciseness for Water buffer dataset from Czech Republic @PSNC took 0.5295424461364746s
Security | Sign check for Water buffer dataset from Czech Republic @PSNC took 0.754586935043335s
Availability | Check URIs Dereferenciability for Water buffer dataset from Czech Republic @PSNC took 9.614798545837402s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.7047600746154785s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.02137160301208496s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 4.124641418457031e-05s
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.1920928955078125e-05s
INFO | --- Analysis for Water_Buffer took 2244.0662970542908s
Availability | SPARQL endpoint availability check for WebIsALOD took 11.73664903640747s
Availability | VoID file availability check for WebIsALOD took 0.0006229877471923828s
Extra | Recovery of all triples for WebIsALOD took 34.14712691307068s
Performance | Total latancy measurement for WebIsALOD took 117.03774976730347s
Amount of data | Number of triples check for WebIsALOD took 45.010504961013794s
Interoperability | New terms check for WebIsALOD took 52.57331824302673s
Versatility | Languages check for WebIsALOD took 10.066238164901733s
Interpretability | Number of blank nodes check for WebIsALOD took 11.469358205795288s
Interpretability | RDF structures check for WebIsALOD took 0.8182108402252197s
Versatility | Serialization formats check for WebIsALOD took 4.076817989349365s
Availability | RDF dump link check for WebIsALOD took 1.6008048057556152s
License | MR license check for WebIsALOD took 25.462090730667114s
License | HR license check for WebIsALOD took 26.16412925720215s
Amount of data | Number of property check for WebIsALOD took 9.879592895507812s
Understandability | Number of label check for WebIsALOD took 2.1020116806030273s
Understandability | URI regex check for WebIsALOD took 14.725000619888306s
Understandability | Vocabs check for WebIsALOD took 2.791294813156128s
Verifiability | Authors check for WebIsALOD took 53.89248275756836s
Verifiability | Publishers check for WebIsALOD took 1.713771104812622s
Performance | Throughput check for WebIsALOD took 99.67526626586914s
Amount of data | Check the number of entities for WebIsALOD took 7.05718994140625e-05s
Verifiability | Contribs. check for WebIsALOD took 0.13701796531677246s
Interlinking | sameAs chians check for WebIsALOD took 0.2085433006286621s
Interlinking | skos check for WebIsALOD took 0.14496922492980957s
Interlinking | skos check for WebIsALOD took 0.08475756645202637s
Timeliness | dataset update frequency check for WebIsALOD took 0.1775045394897461s
Currency | Creation date check for WebIsALOD took 0.2802555561065674s
Currency | Modification date check for WebIsALOD took 0.23218965530395508s
Rep.Conc. | URIs length for WebIsALOD took 56.18185758590698s
Interoperability | New vocabularies check for WebIsALOD took 32.80867838859558s
Consistency | Deprecated classes/propertiers check for WebIsALOD took 11.778798341751099s
Accuracy | Check Functional Property for WebIsALOD took 0.7010135650634766s
Accuracy | Check Inverse Functional Property for WebIsALOD took 0.10775256156921387s
Accuracy | Check Empty annotation labels for WebIsALOD took 1.2258739471435547s
Accuracy | Check White space in annotation for WebIsALOD took 0.030253171920776367s
Accuracy | Check Datatype consistency for WebIsALOD took 0.02799248695373535s
Consistency | Disjoint class check for WebIsALOD took 8.025839567184448s
Consistency | Check Misplaced properties for WebIsALOD took 115.22340941429138s
Consistency | Misplaced classes for WebIsALOD took 31.97284984588623s
Consistency | Check Ontology hijacking for WebIsALOD took 2.2680158615112305s
Consistency | Check Invalid usage of undefined classes for WebIsALOD took 1.3206839561462402s
Consistency | Check Invalid usage of undefined properties for WebIsALOD took 77.13913083076477s
Conciseness | Check Extensional conciseness for WebIsALOD took 0.032024383544921875s
Conciseness | Check Intensional conciseness for WebIsALOD took 7.348691701889038s
Security | Sign check for WebIsALOD took 0.11170744895935059s
Availability | Check URIs Dereferenciability for WebIsALOD took 9.21779179573059s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.4059014320373535s
Reputation | Calculation of the PageRank for WebIsALOD took 0.021249771118164062s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 8.249282836914062e-05s
Interoperability | Check the re-using of existing vocabs for WebIsALOD took 4.121389150619507s
Believability | Calculation of trust value for WebIsALOD took 1.1682510375976562e-05s
INFO | --- Analysis for webisalod took 1406.769559621811s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 9.5367431640625e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.2787504196166992s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.021241188049316406s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 4.696846008300781e-05s
Believability | Calculation of trust value for webnmasunotraveler took 1.2636184692382812e-05s
INFO | --- Analysis for webnmasunotraveler took 8.7181077003479s
Availability | SPARQL endpoint availability check for Whisky Circle took 8.7738037109375e-05s
Availability | VoID file availability check for Whisky Circle took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.271651029586792s
Reputation | Calculation of the PageRank for Whisky Circle took 0.021164894104003906s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00010180473327636719s
Believability | Calculation of trust value for Whisky Circle took 9.775161743164062e-06s
INFO | --- Analysis for whisky-circle-info took 2.9220352172851562s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 17.262054681777954s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.2732808589935303s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.020807266235351562s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 3.5762786865234375e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 5.7220458984375e-06s
INFO | --- Analysis for WHOnto took 35.51679515838623s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.2684755325317383s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.02271294593811035s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 2.9802322387695312e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for whonto took 8.802748918533325s
Availability | SPARQL endpoint availability check for Wikidata took 26.671949863433838s
Availability | VoID file availability check for Wikidata took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for Wikidata took 0.32293272018432617s
Reputation | Calculation of the PageRank for Wikidata took 0.02162003517150879s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.00028967857360839844s
Believability | Calculation of trust value for Wikidata took 8.106231689453125e-06s
INFO | --- Analysis for wikidata took 44.22237229347229s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 8.535385131835938e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.2711341381072998s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.021794795989990234s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 7.05718994140625e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 1.0728836059570312e-05s
INFO | --- Analysis for wikilinks-rdf-nif took 2.4715473651885986s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.2519102096557617s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.26950788497924805s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.021503448486328125s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.416175842285156e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 1.049041748046875e-05s
INFO | --- Analysis for wiktionary-dbpedia-org took 4.21913480758667s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2122926712036133s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.2793424129486084s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.02176380157470703s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 3.337860107421875e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.4332275390625e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 1.0728836059570312e-05s
INFO | --- Analysis for wl-kg took 3.9352574348449707s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 4.0531158447265625e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.27224063873291016s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.02263355255126953s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 7.271766662597656e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 1.0013580322265625e-05s
INFO | --- Analysis for wn-wiki-instances took 3.2560482025146484s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.10221409797668457s
Availability | VoID file availability check for World Loanword Database took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.27803707122802734s
Reputation | Calculation of the PageRank for World Loanword Database took 0.02228689193725586s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 7.224082946777344e-05s
Believability | Calculation of trust value for World Loanword Database took 9.5367431640625e-06s
INFO | --- Analysis for wold took 2.597769021987915s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 4.172325134277344e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.2640571594238281s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.021806001663208008s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 3.9577484130859375e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.0013580322265625e-05s
INFO | --- Analysis for woodtrick took 2.9473180770874023s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 0.44287967681884766s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.27278733253479004s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.021209001541137695s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 3.981590270996094e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for WordFormationLatin took 3.8500237464904785s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 4.1484832763671875e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.26931071281433105s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.020883560180664062s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.00010442733764648438s
Believability | Calculation of trust value for WordLift Blog EN took 1.0251998901367188e-05s
INFO | --- Analysis for wordlift-io-blog-en took 2.8924126625061035s
Availability | SPARQL endpoint availability check for WordLift IT took 8.535385131835938e-05s
Availability | VoID file availability check for WordLift IT took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.26925110816955566s
Reputation | Calculation of the PageRank for WordLift IT took 0.021051883697509766s
Interlinking | Calculation of Degree of Connection for WordLift IT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordLift IT took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00010776519775390625s
Believability | Calculation of trust value for WordLift IT took 1.0728836059570312e-05s
INFO | --- Analysis for wordlift-io-blog-it took 2.8625881671905518s
Availability | SPARQL endpoint availability check for WordNet-RDF took 4.935264587402344e-05s
Availability | VoID file availability check for WordNet-RDF took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.2710886001586914s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.02095627784729004s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.250640869140625e-05s
Believability | Calculation of trust value for WordNet-RDF took 9.775161743164062e-06s
INFO | --- Analysis for wordnet-rdf took 2.4472310543060303s
Availability | SPARQL endpoint availability check for wordpress took 8.440017700195312e-05s
Availability | VoID file availability check for wordpress took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for wordpress took 0.2704763412475586s
Reputation | Calculation of the PageRank for wordpress took 0.022640466690063477s
Interlinking | Calculation of Degree of Connection for wordpress took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for wordpress took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.58306884765625e-05s
Believability | Calculation of trust value for wordpress took 1.1920928955078125e-05s
INFO | --- Analysis for wordpress took 2.887171506881714s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 0.22899508476257324s
Availability | VoID file availability check for World Bank Linked Data took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.2583305835723877s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.022173404693603516s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.0001266002655029297s
Believability | Calculation of trust value for World Bank Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for world-bank-linked-data took 2.7282063961029053s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 0.9299719333648682s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.289013147354126s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.02067279815673828s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.940696716308594e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 7.62939453125e-06s
INFO | --- Analysis for world-factbook-fu-berlin took 4.943727254867554s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 8.58306884765625e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0007781982421875s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.26860594749450684s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.021178722381591797s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.797645568847656e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 9.298324584960938e-06s
INFO | --- Analysis for world-wide-web-foundation took 5.61713433265686s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.3695485591888428s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0005829334259033203s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 2.4861838817596436s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.7787001132965088s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.23096942901611328s
Interoperability | New terms check for World War 1 as Linked Open Data took 1.8558063507080078s
Versatility | Languages check for World War 1 as Linked Open Data took 0.3590199947357178s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.23164582252502441s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.37931275367736816s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.308866024017334s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.21001172065734863s
Availability | RDF dump link check for World War 1 as Linked Open Data took 6.435381889343262s
License | MR license check for World War 1 as Linked Open Data took 0.18845152854919434s
License | HR license check for World War 1 as Linked Open Data took 1.6123688220977783s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.18140053749084473s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.39345717430114746s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.6669845581054688s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.33240723609924316s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.18283653259277344s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.1829395294189453s
Performance | Throughput check for World War 1 as Linked Open Data took 10.672125577926636s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.07049083709716797s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.18493103981018066s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.21451425552368164s
Interlinking | skos check for World War 1 as Linked Open Data took 0.18662166595458984s
Interlinking | skos check for World War 1 as Linked Open Data took 0.15072345733642578s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.1878032684326172s
Currency | Creation date check for World War 1 as Linked Open Data took 0.3703901767730713s
Currency | Modification date check for World War 1 as Linked Open Data took 0.18630671501159668s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 1.954707145690918s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 7.2526068687438965s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.2176511287689209s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.18433094024658203s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.15191245079040527s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.1036429405212402s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.05051255226135254s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.3128337860107422s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.1869823932647705s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.5737380981445312s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 1.8464186191558838s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.11381196975708s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.3479118347167969s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.18709015846252441s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.6651039123535156s
Security | Sign check for World War 1 as Linked Open Data took 0.17595362663269043s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1461.9538309574127s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.5142576694488525s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.022341251373291016s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 9.870529174804688e-05s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 869.3348298072815s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 1.1920928955078125e-05s
INFO | --- Analysis for ww1lod took 2405.0689833164215s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.32477903366088867s
Availability | VoID file availability check for xLiD-Lexica took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.29004573822021484s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.02122044563293457s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 7.033348083496094e-05s
Believability | Calculation of trust value for xLiD-Lexica took 1.1205673217773438e-05s
INFO | --- Analysis for xlid-lexica took 4.004019498825073s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 8.606910705566406e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.2633640766143799s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.021740436553955078s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 4.267692565917969e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 1.33514404296875e-05s
INFO | --- Analysis for xwn took 2.6996419429779053s
Availability | SPARQL endpoint availability check for xxx took 4.673004150390625e-05s
Availability | VoID file availability check for xxx took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for xxx took 0.27123427391052246s
Reputation | Calculation of the PageRank for xxx took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for xxx took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for xxx took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for xxx took 3.0517578125e-05s
Believability | Calculation of trust value for xxx took 1.049041748046875e-05s
INFO | --- Analysis for xx took 2.4961278438568115s
Availability | SPARQL endpoint availability check for YAGO took 0.00012636184692382812s
Availability | VoID file availability check for YAGO took 0.0007436275482177734s
Completeness | Calculation of interlinking completeness for YAGO took 0.26783180236816406s
Reputation | Calculation of the PageRank for YAGO took 0.02070903778076172s
Interlinking | Calculation of Degree of Connection for YAGO took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0009400844573974609s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.00017833709716796875s
Believability | Calculation of trust value for YAGO took 1.1920928955078125e-05s
INFO | --- Analysis for yago took 4.459149122238159s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 19.949792861938477s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.27274441719055176s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.02230358123779297s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 8.344650268554688e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 1.2636184692382812e-05s
INFO | --- Analysis for yahoo_geoplanet took 89.06230878829956s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.14091849327087402s
Availability | VoID file availability check for Yale Senselab took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.2844984531402588s
Reputation | Calculation of the PageRank for Yale Senselab took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 2.9325485229492188e-05s
Believability | Calculation of trust value for Yale Senselab took 1.1444091796875e-05s
INFO | --- Analysis for yale_senselab took 12.519560813903809s
Availability | SPARQL endpoint availability check for test-dapp-2 took 4.267692565917969e-05s
Availability | VoID file availability check for test-dapp-2 took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.27723169326782227s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.02032613754272461s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 2.8848648071289062e-05s
Believability | Calculation of trust value for test-dapp-2 took 1.1682510375976562e-05s
INFO | --- Analysis for yordhis took 2.4157824516296387s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 0.8769118785858154s
Availability | VoID file availability check for Yovisto - academic video search took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.2744114398956299s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.67572021484375e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 9.059906005859375e-06s
INFO | --- Analysis for yovisto took 24.22456979751587s
Availability | SPARQL endpoint availability check for YSA - General Finnish Thesaurus took 0.00012564659118652344s
Availability | VoID file availability check for YSA - General Finnish Thesaurus took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for YSA - General Finnish Thesaurus took 0.2782020568847656s
Reputation | Calculation of the PageRank for YSA - General Finnish Thesaurus took 0.021723508834838867s
Interlinking | Calculation of Degree of Connection for YSA - General Finnish Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for YSA - General Finnish Thesaurus took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for YSA - General Finnish Thesaurus took 3.743171691894531e-05s
Believability | Calculation of trust value for YSA - General Finnish Thesaurus took 1.3589859008789062e-05s
INFO | --- Analysis for ysa took 4.562579154968262s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0003895759582519531s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.26286840438842773s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.173683166503906e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 5.245208740234375e-06s
INFO | --- Analysis for yso took 4.771288156509399s
Availability | SPARQL endpoint availability check for yso-fi-allars took 9.369850158691406e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0008637905120849609s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.280895471572876s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.02122807502746582s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.743171691894531e-05s
Believability | Calculation of trust value for yso-fi-allars took 1.2636184692382812e-05s
INFO | --- Analysis for yso-fi-allars took 3.3261990547180176s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 0.0006051063537597656s
Availability | VoID file availability check for yso-fi-ysa took 0.0007119178771972656s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.2709500789642334s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.022037506103515625s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.552436828613281e-05s
Believability | Calculation of trust value for yso-fi-ysa took 1.2159347534179688e-05s
INFO | --- Analysis for yso-fi-ysa took 3.121042490005493s
Availability | SPARQL endpoint availability check for YSO places took 0.605513334274292s
Availability | VoID file availability check for YSO places took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for YSO places took 0.26950573921203613s
Reputation | Calculation of the PageRank for YSO places took 0.020651578903198242s
Interlinking | Calculation of Degree of Connection for YSO places took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for YSO places took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for YSO places took 3.147125244140625e-05s
Believability | Calculation of trust value for YSO places took 1.0013580322265625e-05s
INFO | --- Analysis for yso-paikat took 3.9442667961120605s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 4.124641418457031e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.30860161781311035s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.02207493782043457s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.6716461181640625e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 1.0013580322265625e-05s
INFO | --- Analysis for zaragoza-datosabiertos took 5.7108848094940186s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 8.535385131835938e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.27491259574890137s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.023381948471069336s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.62396240234375e-05s
Believability | Calculation of trust value for zaragoza_turruta took 1.1920928955078125e-05s
INFO | --- Analysis for zaragoza_turruta took 2.6319146156311035s
Availability | SPARQL endpoint availability check for ZBW Labs took 0.00010061264038085938s
Availability | VoID file availability check for ZBW Labs took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.29204869270324707s
Reputation | Calculation of the PageRank for ZBW Labs took 0.020818233489990234s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 6.914138793945312e-05s
Believability | Calculation of trust value for ZBW Labs took 1.3113021850585938e-05s
INFO | --- Analysis for zbw-labs took 3.322232723236084s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.1548166275024414s
Availability | VoID file availability check for 20th Century Press Archives took 0.0006237030029296875s
Extra | Recovery of all triples for 20th Century Press Archives took 35.734601736068726s
Performance | Total latancy measurement for 20th Century Press Archives took 0.655259370803833s
Amount of data | Number of triples check for 20th Century Press Archives took 2.1621131896972656s
Interoperability | New terms check for 20th Century Press Archives took 1.8248441219329834s
Versatility | Languages check for 20th Century Press Archives took 6.287412166595459s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.8711550235748291s
Interpretability | RDF structures check for 20th Century Press Archives took 0.13190484046936035s
Versatility | Serialization formats check for 20th Century Press Archives took 0.1314234733581543s
Availability | RDF dump link check for 20th Century Press Archives took 0.14983415603637695s
License | MR license check for 20th Century Press Archives took 0.1316225528717041s
License | HR license check for 20th Century Press Archives took 5.200679063796997s
Amount of data | Number of property check for 20th Century Press Archives took 0.14757370948791504s
Understandability | Number of label check for 20th Century Press Archives took 0.5646829605102539s
Understandability | URI regex check for 20th Century Press Archives took 0.2593386173248291s
Understandability | Vocabs check for 20th Century Press Archives took 0.14305567741394043s
Verifiability | Authors check for 20th Century Press Archives took 0.12431788444519043s
Verifiability | Publishers check for 20th Century Press Archives took 0.15741229057312012s
Performance | Throughput check for 20th Century Press Archives took 10.734904289245605s
Amount of data | Check the number of entities for 20th Century Press Archives took 7.748603820800781e-05s
Verifiability | Contribs. check for 20th Century Press Archives took 0.14560294151306152s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.12809062004089355s
Interlinking | skos check for 20th Century Press Archives took 0.17343926429748535s
Interlinking | skos check for 20th Century Press Archives took 0.16355419158935547s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.1293315887451172s
Currency | Creation date check for 20th Century Press Archives took 0.2593715190887451s
Currency | Modification date check for 20th Century Press Archives took 0.26751184463500977s
Rep.Conc. | URIs length for 20th Century Press Archives took 14.62474775314331s
Interoperability | New vocabularies check for 20th Century Press Archives took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.14029455184936523s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.12882494926452637s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.14684462547302246s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 5.262240648269653s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.882439374923706s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.042371034622192s
Consistency | Disjoint class check for 20th Century Press Archives took 0.14110708236694336s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.129448413848877s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.2932403087615967s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 6.892953634262085s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.2961764335632324s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.7099661827087402s
Security | Sign check for 20th Century Press Archives took 0.1481318473815918s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 1034.4722862243652s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.3417787551879883s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.021861553192138672s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00011229515075683594s
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 1164.3430633544922s
Availability | SPARQL endpoint availability check for zhishi.lemon took 4.482269287109375e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.2871880531311035s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.022634267807006836s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0010840892791748047s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 6.175041198730469e-05s
Believability | Calculation of trust value for zhishi.lemon took 1.1920928955078125e-05s
INFO | --- Analysis for zhishi-lemon took 4.752951622009277s
Availability | SPARQL endpoint availability check for Zhishi.me took 7.733465671539307s
Availability | VoID file availability check for Zhishi.me took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.2645571231842041s
Reputation | Calculation of the PageRank for Zhishi.me took 0.021234512329101562s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 6.914138793945312e-05s
Believability | Calculation of trust value for Zhishi.me took 1.3113021850585938e-05s
INFO | --- Analysis for zhishi-me took 12.724295616149902s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 0.00010037422180175781s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0007507801055908203s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.2658522129058838s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.021280765533447266s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 6.771087646484375e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 1.1444091796875e-05s
INFO | --- Analysis for zitgist-musicbrainz took 2.778562545776367s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 4.4345855712890625e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.264693021774292s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.023040056228637695s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 3.170967102050781e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 1.1444091796875e-05s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 2.749814748764038s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.2696998119354248s
Availability | VoID file availability check for performing-arts.ch took 0.0005156993865966797s
Extra | Recovery of all triples for performing-arts.ch took 17.10932445526123s
Performance | Total latancy measurement for performing-arts.ch took 0.6924190521240234s
Amount of data | Number of triples check for performing-arts.ch took 30.81883978843689s
Interoperability | New terms check for performing-arts.ch took 1.4750592708587646s
Versatility | Languages check for performing-arts.ch took 60.123152017593384s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.11916995048523s
Interpretability | RDF structures check for performing-arts.ch took 0.9114692211151123s
Versatility | Serialization formats check for performing-arts.ch took 0.15427255630493164s
Availability | RDF dump link check for performing-arts.ch took 0.14471173286437988s
License | MR license check for performing-arts.ch took 0.14121484756469727s
License | HR license check for performing-arts.ch took 60.11330032348633s
Amount of data | Number of property check for performing-arts.ch took 0.15611028671264648s
Understandability | Number of label check for performing-arts.ch took 7.358696937561035s
Understandability | URI regex check for performing-arts.ch took 0.293790340423584s
Understandability | Vocabs check for performing-arts.ch took 0.144758939743042s
Verifiability | Authors check for performing-arts.ch took 0.14048409461975098s
Verifiability | Publishers check for performing-arts.ch took 0.13995671272277832s
Performance | Throughput check for performing-arts.ch took 10.977527379989624s
Amount of data | Check the number of entities for performing-arts.ch took 6.842613220214844e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.15027379989624023s
Interlinking | sameAs chians check for performing-arts.ch took 0.5200052261352539s
Interlinking | skos check for performing-arts.ch took 0.1733713150024414s
Interlinking | skos check for performing-arts.ch took 0.14105844497680664s
Timeliness | dataset update frequency check for performing-arts.ch took 0.14579296112060547s
Currency | Creation date check for performing-arts.ch took 0.29384851455688477s
Currency | Modification date check for performing-arts.ch took 0.29321765899658203s
Rep.Conc. | URIs length for performing-arts.ch took 21.460954904556274s
Interoperability | New vocabularies check for performing-arts.ch took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.13933753967285156s
Accuracy | Check Functional Property for performing-arts.ch took 0.13898038864135742s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.13901352882385254s
Accuracy | Check Empty annotation labels for performing-arts.ch took 10.56532073020935s
Accuracy | Check White space in annotation for performing-arts.ch took 2.50954008102417s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.806884050369263s
Consistency | Disjoint class check for performing-arts.ch took 0.13614630699157715s
Consistency | Check Misplaced properties for performing-arts.ch took 0.38716721534729004s
Consistency | Misplaced classes for performing-arts.ch took 8.470479965209961s
Consistency | Check Ontology hijacking for performing-arts.ch took 49.106704235076904s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 16936.167513370514s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.8005869388580322s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.824465036392212s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.29248976707458496s
Security | Sign check for performing-arts.ch took 0.14201974868774414s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.3778178691864014s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.6445178985595703s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.022072315216064453s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 2.765655517578125e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.6450881958007812e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 2.1457672119140625e-06s
Believability | Calculation of trust value for performing-arts.ch took 1.1444091796875e-05s
INFO | --- Analysis for performing-arts.ch took 17735.599463701248s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 1.9929301738739014s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.27057790756225586s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.020512819290161133s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.1205673217773438e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for The-AA-Thesaurus took 8.04042387008667s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.4085309505462646s
Availability | VoID file availability check for MiMoTextBase took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.27342748641967773s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.020696401596069336s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.52587890625e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.1205673217773438e-05s
Believability | Calculation of trust value for MiMoTextBase took 1.0967254638671875e-05s
INFO | --- Analysis for MiMoTextBase took 6.527177572250366s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.4544391632080078s
Availability | VoID file availability check for National Library of Sweden took 0.000530242919921875s
Extra | Recovery of all triples for National Library of Sweden took 6.329591989517212s
Performance | Total latancy measurement for National Library of Sweden took 0.9996662139892578s
Amount of data | Number of triples check for National Library of Sweden took 32.18490219116211s
Interoperability | New terms check for National Library of Sweden took 31.669824600219727s
Versatility | Languages check for National Library of Sweden took 0.19304585456848145s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.1676301956177s
Interpretability | RDF structures check for National Library of Sweden took 0.5813682079315186s
Versatility | Serialization formats check for National Library of Sweden took 0.257828950881958s
Availability | RDF dump link check for National Library of Sweden took 0.20372462272644043s
License | MR license check for National Library of Sweden took 0.3240060806274414s
License | HR license check for National Library of Sweden took 0.32500338554382324s
Amount of data | Number of property check for National Library of Sweden took 0.21099352836608887s
Understandability | Number of label check for National Library of Sweden took 0.8068866729736328s
Understandability | URI regex check for National Library of Sweden took 0.6390900611877441s
Understandability | Vocabs check for National Library of Sweden took 0.20099663734436035s
Verifiability | Authors check for National Library of Sweden took 0.25516176223754883s
Verifiability | Publishers check for National Library of Sweden took 0.24438691139221191s
Performance | Throughput check for National Library of Sweden took 11.597117185592651s
Amount of data | Check the number of entities for National Library of Sweden took 7.2479248046875e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.21943187713623047s
Interlinking | sameAs chians check for National Library of Sweden took 0.28275346755981445s
Interlinking | skos check for National Library of Sweden took 0.6817424297332764s
Interlinking | skos check for National Library of Sweden took 0.19415044784545898s
Timeliness | dataset update frequency check for National Library of Sweden took 0.20583009719848633s
Currency | Creation date check for National Library of Sweden took 0.5669205188751221s
Currency | Modification date check for National Library of Sweden took 0.520395040512085s
Rep.Conc. | URIs length for National Library of Sweden took 81.22129106521606s
Interoperability | New vocabularies check for National Library of Sweden took 5.7220458984375e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.19356083869934082s
Accuracy | Check Functional Property for National Library of Sweden took 0.28013157844543457s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.28098154067993164s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.2730085849761963s
Consistency | Disjoint class check for National Library of Sweden took 0.19066643714904785s
Consistency | Check Misplaced properties for National Library of Sweden took 60.17219948768616s
Consistency | Misplaced classes for National Library of Sweden took 1.111938238143921s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.2793564796447754s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.2683441638946533s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 61.3173942565918s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.28147196769714355s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.329575777053833s
Security | Sign check for National Library of Sweden took 0.3245365619659424s
Availability | Check URIs Dereferenciability for National Library of Sweden took 13.333211898803711s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.3579897880554199s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.021089553833007812s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 6.437301635742188e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0006797313690185547s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.6450881958007812e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.3828277587890625e-05s
INFO | --- Analysis for NLS took 1430.237716436386s
Availability | SPARQL endpoint availability check for Japan Search took 1.3623979091644287s
Availability | VoID file availability check for Japan Search took 0.000545501708984375s
Extra | Recovery of all triples for Japan Search took 3.4257609844207764s
Performance | Total latancy measurement for Japan Search took 2.256019353866577s
Amount of data | Number of triples check for Japan Search took 7.996790647506714s
Interoperability | New terms check for Japan Search took 4.115685701370239s
Versatility | Languages check for Japan Search took 0.7124137878417969s
Interpretability | Number of blank nodes check for Japan Search took 12.121651411056519s
Interpretability | RDF structures check for Japan Search took 0.8153724670410156s
Versatility | Serialization formats check for Japan Search took 0.3432650566101074s
Availability | RDF dump link check for Japan Search took 0.2876577377319336s
License | MR license check for Japan Search took 1.6065330505371094s
License | HR license check for Japan Search took 12.277174234390259s
Amount of data | Number of property check for Japan Search took 0.7170987129211426s
Understandability | Number of label check for Japan Search took 2.574873924255371s
Understandability | URI regex check for Japan Search took 0.9756777286529541s
Understandability | Vocabs check for Japan Search took 0.2629263401031494s
Verifiability | Authors check for Japan Search took 0.320817232131958s
Verifiability | Publishers check for Japan Search took 0.2978329658508301s
Performance | Throughput check for Japan Search took 10.934350728988647s
Amount of data | Check the number of entities for Japan Search took 6.961822509765625e-05s
Verifiability | Contribs. check for Japan Search took 0.29462599754333496s
Interlinking | sameAs chians check for Japan Search took 0.27585506439208984s
Interlinking | skos check for Japan Search took 0.44063663482666016s
Interlinking | skos check for Japan Search took 0.26319289207458496s
Timeliness | dataset update frequency check for Japan Search took 0.33732104301452637s
Currency | Creation date check for Japan Search took 0.5882112979888916s
Currency | Modification date check for Japan Search took 0.5788986682891846s
Rep.Conc. | URIs length for Japan Search took 14.3195641040802s
Interoperability | New vocabularies check for Japan Search took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.26519346237182617s
Accuracy | Check Functional Property for Japan Search took 0.31371402740478516s
Accuracy | Check Inverse Functional Property for Japan Search took 0.7606735229492188s
Accuracy | Check Empty annotation labels for Japan Search took 1.528825283050537s
Accuracy | Check White space in annotation for Japan Search took 0.029082059860229492s
Accuracy | Check Datatype consistency for Japan Search took 0.02871227264404297s
Consistency | Disjoint class check for Japan Search took 0.31476330757141113s
Consistency | Check Misplaced properties for Japan Search took 10.760689973831177s
Consistency | Misplaced classes for Japan Search took 0.35327720642089844s
Consistency | Check Ontology hijacking for Japan Search took 3.4193994998931885s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.287116527557373s
Consistency | Check Invalid usage of undefined properties for Japan Search took 11.56581425666809s
Conciseness | Check Extensional conciseness for Japan Search took 0.03516721725463867s
Conciseness | Check Intensional conciseness for Japan Search took 0.943666934967041s
Security | Sign check for Japan Search took 0.27834510803222656s
Availability | Check URIs Dereferenciability for Japan Search took 11.157026052474976s
Completeness | Calculation of interlinking completeness for Japan Search took 0.2769899368286133s
Reputation | Calculation of the PageRank for Japan Search took 0.021259069442749023s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Japan Search took 1.1920928955078125e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 1.430511474609375e-06s
Believability | Calculation of trust value for Japan Search took 1.0967254638671875e-05s
INFO | --- Analysis for Japan-Search took 388.60218334198s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.0456607341766357s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.27059292793273926s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.020995616912841797s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.049041748046875e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.0967254638671875e-05s
INFO | --- Analysis for Rijksmuseum took 4.800808668136597s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.42790889739990234s
Availability | VoID file availability check for Finnish Public Libraries took 0.00034117698669433594s
Extra | Recovery of all triples for Finnish Public Libraries took 14.90944528579712s
Performance | Total latancy measurement for Finnish Public Libraries took 1.2147314548492432s
Amount of data | Number of triples check for Finnish Public Libraries took 53.43001675605774s
Interoperability | New terms check for Finnish Public Libraries took 13.149441003799438s
Versatility | Languages check for Finnish Public Libraries took 60.10580539703369s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 51.3404746055603s
Interpretability | RDF structures check for Finnish Public Libraries took 0.7775914669036865s
Versatility | Serialization formats check for Finnish Public Libraries took 0.40700340270996094s
Availability | RDF dump link check for Finnish Public Libraries took 0.2050769329071045s
License | MR license check for Finnish Public Libraries took 0.2582414150238037s
License | HR license check for Finnish Public Libraries took 33.29070067405701s
Amount of data | Number of property check for Finnish Public Libraries took 0.2620570659637451s
Understandability | Number of label check for Finnish Public Libraries took 11.506742238998413s
Understandability | URI regex check for Finnish Public Libraries took 0.4562671184539795s
Understandability | Vocabs check for Finnish Public Libraries took 0.25302815437316895s
Verifiability | Authors check for Finnish Public Libraries took 0.2542588710784912s
Verifiability | Publishers check for Finnish Public Libraries took 0.24898457527160645s
Performance | Throughput check for Finnish Public Libraries took 11.50120735168457s
Amount of data | Check the number of entities for Finnish Public Libraries took 6.794929504394531e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.2517707347869873s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.29532957077026367s
Interlinking | skos check for Finnish Public Libraries took 0.2657468318939209s
Interlinking | skos check for Finnish Public Libraries took 0.24971365928649902s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.25569701194763184s
Currency | Creation date check for Finnish Public Libraries took 0.5061345100402832s
Currency | Modification date check for Finnish Public Libraries took 0.37343597412109375s
Rep.Conc. | URIs length for Finnish Public Libraries took 72.88565802574158s
Interoperability | New vocabularies check for Finnish Public Libraries took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.24158358573913574s
Accuracy | Check Functional Property for Finnish Public Libraries took 0.37780046463012695s
Accuracy | Check Inverse Functional Property for Finnish Public Libraries took 0.40786004066467285s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 7.814651250839233s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.1604368686676025s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.37812352180481s
Consistency | Disjoint class check for Finnish Public Libraries took 0.25214076042175293s
Consistency | Check Misplaced properties for Finnish Public Libraries took 55.21580457687378s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 13.245961666107178s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.535923957824707s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 52.789605140686035s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.7260708808898926s
Security | Sign check for Finnish Public Libraries took 0.3480417728424072s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 1.737229824066162s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.3844025135040283s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.021999835968017578s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0010933876037597656s
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 1.6689300537109375e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 1.2159347534179688e-05s
INFO | --- Analysis for FI-Library took 655.2902090549469s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 2.5972955226898193s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0005042552947998047s
Extra | Recovery of all triples for Shanghai Library Open Data Platform took 8.67601490020752s
Performance | Total latancy measurement for Shanghai Library Open Data Platform took 3.5135037899017334s
Amount of data | Number of triples check for Shanghai Library Open Data Platform took 1.692901849746704s
Interoperability | New terms check for Shanghai Library Open Data Platform took 4.922987937927246s
Versatility | Languages check for Shanghai Library Open Data Platform took 60.68316602706909s
Interpretability | Number of blank nodes check for Shanghai Library Open Data Platform took 16.035379886627197s
Interpretability | RDF structures check for Shanghai Library Open Data Platform took 1.1548805236816406s
Versatility | Serialization formats check for Shanghai Library Open Data Platform took 0.854865550994873s
Availability | RDF dump link check for Shanghai Library Open Data Platform took 0.7553601264953613s
License | MR license check for Shanghai Library Open Data Platform took 1.0755138397216797s
License | HR license check for Shanghai Library Open Data Platform took 36.64647364616394s
Amount of data | Number of property check for Shanghai Library Open Data Platform took 0.6991877555847168s
Understandability | Number of label check for Shanghai Library Open Data Platform took 1.4092085361480713s
Understandability | URI regex check for Shanghai Library Open Data Platform took 1.538947343826294s
Understandability | Vocabs check for Shanghai Library Open Data Platform took 0.7442903518676758s
Verifiability | Authors check for Shanghai Library Open Data Platform took 0.8398687839508057s
Verifiability | Publishers check for Shanghai Library Open Data Platform took 0.7663314342498779s
Performance | Throughput check for Shanghai Library Open Data Platform took 13.776077508926392s
Amount of data | Check the number of entities for Shanghai Library Open Data Platform took 7.605552673339844e-05s
Verifiability | Contribs. check for Shanghai Library Open Data Platform took 0.7229044437408447s
Interlinking | sameAs chians check for Shanghai Library Open Data Platform took 0.7227201461791992s
Interlinking | skos check for Shanghai Library Open Data Platform took 1.018963098526001s
Interlinking | skos check for Shanghai Library Open Data Platform took 0.719921350479126s
Timeliness | dataset update frequency check for Shanghai Library Open Data Platform took 0.7946882247924805s
Currency | Creation date check for Shanghai Library Open Data Platform took 1.4603149890899658s
Currency | Modification date check for Shanghai Library Open Data Platform took 1.4868383407592773s
Rep.Conc. | URIs length for Shanghai Library Open Data Platform took 9.9210205078125s
Interoperability | New vocabularies check for Shanghai Library Open Data Platform took 6.67572021484375e-06s
Consistency | Deprecated classes/propertiers check for Shanghai Library Open Data Platform took 0.6874313354492188s
Accuracy | Check Functional Property for Shanghai Library Open Data Platform took 0.7012758255004883s
Accuracy | Check Inverse Functional Property for Shanghai Library Open Data Platform took 0.7412595748901367s
Accuracy | Check Empty annotation labels for Shanghai Library Open Data Platform took 3.1704351902008057s
Accuracy | Check White space in annotation for Shanghai Library Open Data Platform took 0.15446949005126953s
Accuracy | Check Datatype consistency for Shanghai Library Open Data Platform took 0.13640284538269043s
Consistency | Disjoint class check for Shanghai Library Open Data Platform took 0.82798171043396s
Consistency | Check Misplaced properties for Shanghai Library Open Data Platform took 6.257117033004761s
Consistency | Misplaced classes for Shanghai Library Open Data Platform took 1.3132994174957275s
Consistency | Check Ontology hijacking for Shanghai Library Open Data Platform took 5.163114547729492s
Consistency | Check Invalid usage of undefined classes for Shanghai Library Open Data Platform took 1.4092254638671875s
Consistency | Check Invalid usage of undefined properties for Shanghai Library Open Data Platform took 7.025717258453369s
Conciseness | Check Extensional conciseness for Shanghai Library Open Data Platform took 0.15529131889343262s
Conciseness | Check Intensional conciseness for Shanghai Library Open Data Platform took 1.1930816173553467s
Security | Sign check for Shanghai Library Open Data Platform took 1.257990837097168s
Availability | Check URIs Dereferenciability for Shanghai Library Open Data Platform took 17.031808614730835s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.343402624130249s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.021400928497314453s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.6450881958007812e-05s
Interoperability | Check the re-using of existing vocabs for Shanghai Library Open Data Platform took 2.86102294921875e-06s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 1.2159347534179688e-05s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 335.86219000816345s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.3975491523742676s
Availability | VoID file availability check for National Library Netherlands took 0.0006902217864990234s
Extra | Recovery of all triples for National Library Netherlands took 0.6388216018676758s
Performance | Total latancy measurement for National Library Netherlands took 0.7944037914276123s
Amount of data | Number of triples check for National Library Netherlands took 0.14270806312561035s
Interoperability | New terms check for National Library Netherlands took 1.47707200050354s
Versatility | Languages check for National Library Netherlands took 58.14023232460022s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.17534613609313965s
Interpretability | RDF structures check for National Library Netherlands took 0.15095901489257812s
Versatility | Serialization formats check for National Library Netherlands took 0.1607828140258789s
Availability | RDF dump link check for National Library Netherlands took 0.14630722999572754s
License | MR license check for National Library Netherlands took 0.1627962589263916s
License | HR license check for National Library Netherlands took 0.1735541820526123s
Amount of data | Number of property check for National Library Netherlands took 0.13283061981201172s
Understandability | Number of label check for National Library Netherlands took 0.14673662185668945s
Understandability | URI regex check for National Library Netherlands took 0.3809773921966553s
Understandability | Vocabs check for National Library Netherlands took 0.14972543716430664s
Verifiability | Authors check for National Library Netherlands took 0.1456012725830078s
Verifiability | Publishers check for National Library Netherlands took 0.15033245086669922s
Performance | Throughput check for National Library Netherlands took 10.653390407562256s
Amount of data | Check the number of entities for National Library Netherlands took 7.510185241699219e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.14094781875610352s
Interlinking | sameAs chians check for National Library Netherlands took 0.13478636741638184s
Interlinking | skos check for National Library Netherlands took 0.14099931716918945s
Interlinking | skos check for National Library Netherlands took 0.1525125503540039s
Timeliness | dataset update frequency check for National Library Netherlands took 0.17650079727172852s
Currency | Creation date check for National Library Netherlands took 0.29874682426452637s
Currency | Modification date check for National Library Netherlands took 0.29426050186157227s
Rep.Conc. | URIs length for National Library Netherlands took 0.664315938949585s
Interoperability | New vocabularies check for National Library Netherlands took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.14768457412719727s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.40302252769470215s
Accuracy | Check White space in annotation for National Library Netherlands took 0.027285337448120117s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.027540922164916992s
Consistency | Disjoint class check for National Library Netherlands took 0.1553201675415039s
Consistency | Check Misplaced properties for National Library Netherlands took 0.30493903160095215s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.7605681419372559s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 1.4072761535644531s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.5620396137237549s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.02971506118774414s
Security | Sign check for National Library Netherlands took 0.14998841285705566s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1735.0372939109802s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.7313292026519775s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.02178788185119629s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 1.8835067749023438e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 4.291534423828125e-06s
Believability | Calculation of trust value for National Library Netherlands took 1.0251998901367188e-05s
INFO | --- Analysis for National-Library-Netherlands took 1839.9396312236786s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.4165143966674805s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.2752101421356201s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.021853208541870117s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0008151531219482422s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.3828277587890625e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 9.298324584960938e-06s
INFO | --- Analysis for Antique-Renaissance took 5.363695859909058s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 5.307875871658325s
Availability | VoID file availability check for ARTSDATA.CA took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.2752244472503662s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.021200895309448242s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.3589859008789062e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 1.0013580322265625e-05s
INFO | --- Analysis for ARTSDATA-CA took 10.815831661224365s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.14689850807189941s
Availability | VoID file availability check for Architecture of Knowledge took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.2854890823364258s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.022126197814941406s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.3113021850585938e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 9.775161743164062e-06s
INFO | --- Analysis for ArCo took 3.4347753524780273s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.3570678234100342s
Availability | VoID file availability check for ConfermentSampo took 0.00112152099609375s
Extra | Recovery of all triples for ConfermentSampo took 55.562663316726685s
Performance | Total latancy measurement for ConfermentSampo took 0.7929303646087646s
Amount of data | Number of triples check for ConfermentSampo took 10.684396266937256s
Interoperability | New terms check for ConfermentSampo took 2.648930549621582s
Versatility | Languages check for ConfermentSampo took 29.227575063705444s
Interpretability | Number of blank nodes check for ConfermentSampo took 8.317537307739258s
Security | Check HTTPS for ConfermentSampo took 0.3788466453552246s
Interpretability | RDF structures check for ConfermentSampo took 0.19904398918151855s
Versatility | Serialization formats check for ConfermentSampo took 0.2035384178161621s
Availability | RDF dump link check for ConfermentSampo took 2.909428119659424s
License | MR license check for ConfermentSampo took 0.19068455696105957s
License | HR license check for ConfermentSampo took 0.24138736724853516s
Amount of data | Number of property check for ConfermentSampo took 0.18453693389892578s
Understandability | Number of label check for ConfermentSampo took 5.316611051559448s
Understandability | URI regex check for ConfermentSampo took 0.3616914749145508s
Understandability | Vocabs check for ConfermentSampo took 0.1596367359161377s
Verifiability | Authors check for ConfermentSampo took 0.19384121894836426s
Verifiability | Publishers check for ConfermentSampo took 0.19046831130981445s
Performance | Throughput check for ConfermentSampo took 10.649079322814941s
Amount of data | Check the number of entities for ConfermentSampo took 3.909334897994995s
Verifiability | Contribs. check for ConfermentSampo took 0.16274404525756836s
Interlinking | sameAs chians check for ConfermentSampo took 0.4631164073944092s
Interlinking | skos check for ConfermentSampo took 0.15795397758483887s
Interlinking | skos check for ConfermentSampo took 0.14872407913208008s
Timeliness | dataset update frequency check for ConfermentSampo took 0.1697077751159668s
Currency | Creation date check for ConfermentSampo took 0.3409287929534912s
Currency | Modification date check for ConfermentSampo took 0.34507131576538086s
Rep.Conc. | URIs length for ConfermentSampo took 34.438746213912964s
Interoperability | New vocabularies check for ConfermentSampo took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.19161224365234375s
Accuracy | Check Functional Property for ConfermentSampo took 0.18979239463806152s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.15603852272033691s
Accuracy | Check Empty annotation labels for ConfermentSampo took 14.998271465301514s
Accuracy | Check White space in annotation for ConfermentSampo took 2.99518084526062s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.166063547134399s
Consistency | Disjoint class check for ConfermentSampo took 0.16064214706420898s
Consistency | Check Misplaced properties for ConfermentSampo took 6.3703930377960205s
Consistency | Check Ontology hijacking for ConfermentSampo took 14.961347341537476s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.471693992614746s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.5793557167053223s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.8022637367248535s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.1923360824584961s
Security | Sign check for ConfermentSampo took 0.15590167045593262s
Availability | Check URIs Dereferenciability for ConfermentSampo took 2.3019943237304688s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.4026150703430176s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.020920276641845703s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 2.384185791015625e-06s
Believability | Calculation of trust value for ConfermentSampo took 1.2159347534179688e-05s
INFO | --- Analysis for ConfermentSampo took 350.4939887523651s
Availability | SPARQL endpoint availability check for Museum Finland took 0.9057095050811768s
Availability | VoID file availability check for Museum Finland took 0.00048041343688964844s
Extra | Recovery of all triples for Museum Finland took 14.29135513305664s
Performance | Total latancy measurement for Museum Finland took 0.7821002006530762s
Amount of data | Number of triples check for Museum Finland took 0.34755969047546387s
Interoperability | New terms check for Museum Finland took 1.5545010566711426s
Versatility | Languages check for Museum Finland took 0.6462271213531494s
Interpretability | Number of blank nodes check for Museum Finland took 0.33202123641967773s
Security | Check HTTPS for Museum Finland took 0.23146796226501465s
Interpretability | RDF structures check for Museum Finland took 0.6115837097167969s
Versatility | Serialization formats check for Museum Finland took 0.201066255569458s
Availability | RDF dump link check for Museum Finland took 0.1540546417236328s
License | MR license check for Museum Finland took 0.1977696418762207s
License | HR license check for Museum Finland took 0.3779447078704834s
Amount of data | Number of property check for Museum Finland took 0.18069791793823242s
Understandability | Number of label check for Museum Finland took 0.3504929542541504s
Understandability | URI regex check for Museum Finland took 0.30652332305908203s
Understandability | Vocabs check for Museum Finland took 0.15230965614318848s
Verifiability | Authors check for Museum Finland took 0.15250420570373535s
Verifiability | Publishers check for Museum Finland took 0.1513350009918213s
Performance | Throughput check for Museum Finland took 10.523206233978271s
Amount of data | Check the number of entities for Museum Finland took 7.104873657226562e-05s
Verifiability | Contribs. check for Museum Finland took 0.15286493301391602s
Interlinking | sameAs chians check for Museum Finland took 0.16417646408081055s
Interlinking | skos check for Museum Finland took 0.15315604209899902s
Interlinking | skos check for Museum Finland took 0.15124988555908203s
Timeliness | dataset update frequency check for Museum Finland took 0.1519298553466797s
Currency | Creation date check for Museum Finland took 0.35550618171691895s
Currency | Modification date check for Museum Finland took 0.3498551845550537s
Rep.Conc. | URIs length for Museum Finland took 3.530609369277954s
Interoperability | New vocabularies check for Museum Finland took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.1828911304473877s
Accuracy | Check Functional Property for Museum Finland took 0.15776348114013672s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.1524367332458496s
Accuracy | Check Empty annotation labels for Museum Finland took 0.9560060501098633s
Accuracy | Check White space in annotation for Museum Finland took 0.06136798858642578s
Accuracy | Check Datatype consistency for Museum Finland took 0.9700300693511963s
Consistency | Disjoint class check for Museum Finland took 0.15839815139770508s
Consistency | Check Misplaced properties for Museum Finland took 0.6230120658874512s
Consistency | Check Ontology hijacking for Museum Finland took 2.2799479961395264s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.5875813961029053s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.7836463451385498s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6655666828155518s
Conciseness | Check Intensional conciseness for Museum Finland took 0.24054646492004395s
Security | Sign check for Museum Finland took 0.15151548385620117s
Availability | Check URIs Dereferenciability for Museum Finland took 2781.4319071769714s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.465512752532959s
Reputation | Calculation of the PageRank for Museum Finland took 0.02175307273864746s
Interlinking | Calculation of Degree of Connection for Museum Finland took 2.8848648071289062e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 2.0742416381835938e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 1.9073486328125e-06s
Believability | Calculation of trust value for Museum Finland took 6.67572021484375e-06s
INFO | --- Analysis for FI-Museum took 2844.9209322929382s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.18758702278137207s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0005443096160888672s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 15.781916856765747s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.7762329578399658s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 30.147095680236816s
Interoperability | New terms check for Mapping Manuscript Migrations took 4.9186952114105225s
Versatility | Languages check for Mapping Manuscript Migrations took 75.84746599197388s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 29.59169054031372s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.3806333541870117s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.19008827209472656s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.18361544609069824s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.1518266201019287s
License | MR license check for Mapping Manuscript Migrations took 0.1827538013458252s
License | HR license check for Mapping Manuscript Migrations took 1.7966697216033936s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.18201589584350586s
Understandability | Number of label check for Mapping Manuscript Migrations took 9.007922649383545s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.33419299125671387s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.15275025367736816s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.18393397331237793s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.18146562576293945s
Performance | Throughput check for Mapping Manuscript Migrations took 10.485592365264893s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.051262378692627s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.1513381004333496s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.5093207359313965s
Interlinking | skos check for Mapping Manuscript Migrations took 0.15254592895507812s
Interlinking | skos check for Mapping Manuscript Migrations took 0.14898347854614258s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.15399837493896484s
Currency | Creation date check for Mapping Manuscript Migrations took 0.3333170413970947s
Currency | Modification date check for Mapping Manuscript Migrations took 0.1978161334991455s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 49.70720624923706s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.152510404586792s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.15571951866149902s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.1512908935546875s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 10.664630889892578s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.4136502742767334s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.725777626037598s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.18299579620361328s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 23.823883056640625s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 16.415011882781982s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.5783429145812988s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.576263189315796s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.8027591705322266s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.18570184707641602s
Security | Sign check for Mapping Manuscript Migrations took 0.15148639678955078s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1541.135225534439s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.6014046669006348s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.021169424057006836s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.5497207641601562e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 1.6689300537109375e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 1.1682510375976562e-05s
INFO | --- Analysis for MMM took 1943.8468751907349s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.2829325199127197s
Availability | VoID file availability check for Semantic Kalevala took 0.0005311965942382812s
Extra | Recovery of all triples for Semantic Kalevala took 9.589005947113037s
Performance | Total latancy measurement for Semantic Kalevala took 0.7874031066894531s
Amount of data | Number of triples check for Semantic Kalevala took 0.47478342056274414s
Interoperability | New terms check for Semantic Kalevala took 2.5531423091888428s
Versatility | Languages check for Semantic Kalevala took 0.9475395679473877s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.3709571361541748s
Security | Check HTTPS for Semantic Kalevala took 0.38030290603637695s
Interpretability | RDF structures check for Semantic Kalevala took 0.2506253719329834s
Versatility | Serialization formats check for Semantic Kalevala took 0.18287897109985352s
Availability | RDF dump link check for Semantic Kalevala took 0.1571516990661621s
License | MR license check for Semantic Kalevala took 0.17734098434448242s
License | HR license check for Semantic Kalevala took 1.352583885192871s
Amount of data | Number of property check for Semantic Kalevala took 0.18981409072875977s
Understandability | Number of label check for Semantic Kalevala took 0.46712636947631836s
Understandability | URI regex check for Semantic Kalevala took 0.30664944648742676s
Understandability | Vocabs check for Semantic Kalevala took 0.18156075477600098s
Verifiability | Authors check for Semantic Kalevala took 0.1691761016845703s
Verifiability | Publishers check for Semantic Kalevala took 0.15416479110717773s
Performance | Throughput check for Semantic Kalevala took 10.563407182693481s
Amount of data | Check the number of entities for Semantic Kalevala took 7.2479248046875e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.1655433177947998s
Interlinking | sameAs chians check for Semantic Kalevala took 0.18210101127624512s
Interlinking | skos check for Semantic Kalevala took 0.2706120014190674s
Interlinking | skos check for Semantic Kalevala took 0.14850163459777832s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.165557861328125s
Currency | Creation date check for Semantic Kalevala took 0.34766340255737305s
Currency | Modification date check for Semantic Kalevala took 0.3349032402038574s
Rep.Conc. | URIs length for Semantic Kalevala took 4.869131565093994s
Interoperability | New vocabularies check for Semantic Kalevala took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.18321895599365234s
Accuracy | Check Functional Property for Semantic Kalevala took 0.18495941162109375s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.1518099308013916s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.8018667697906494s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.2939929962158203s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.4050230979919434s
Consistency | Disjoint class check for Semantic Kalevala took 0.1528913974761963s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.8097589015960693s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.270009756088257s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.3693819046020508s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.538520336151123s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.8710694313049316s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.24743318557739258s
Security | Sign check for Semantic Kalevala took 0.16805052757263184s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 2988.299545288086s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.5011608600616455s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.021374940872192383s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.2159347534179688e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 1.430511474609375e-06s
Believability | Calculation of trust value for Semantic Kalevala took 1.0251998901367188e-05s
INFO | --- Analysis for Semantic-Kalevala took 3052.6910133361816s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 1.1543138027191162s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0005662441253662109s
Extra | Recovery of all triples for Smithsonian American Art Museum took 277.3073046207428s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.07133412361145s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5630147457122803s
Interoperability | New terms check for Smithsonian American Art Museum took 4.171620607376099s
Versatility | Languages check for Smithsonian American Art Museum took 26.99152660369873s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.5629096031188965s
Security | Check HTTPS for Smithsonian American Art Museum took 0.35476016998291016s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.7105834484100342s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.573915958404541s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.5935015678405762s
License | MR license check for Smithsonian American Art Museum took 0.614795446395874s
License | HR license check for Smithsonian American Art Museum took 17.75960350036621s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5631682872772217s
Understandability | Number of label check for Smithsonian American Art Museum took 0.5657742023468018s
Understandability | URI regex check for Smithsonian American Art Museum took 1.146909475326538s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.5766172409057617s
Verifiability | Authors check for Smithsonian American Art Museum took 0.5721883773803711s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.6319198608398438s
Performance | Throughput check for Smithsonian American Art Museum took 11.505613088607788s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 7.224082946777344e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.5819036960601807s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.5680627822875977s
Interlinking | skos check for Smithsonian American Art Museum took 0.5610404014587402s
Interlinking | skos check for Smithsonian American Art Museum took 0.5702919960021973s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.5786638259887695s
Currency | Creation date check for Smithsonian American Art Museum took 1.289656400680542s
Currency | Modification date check for Smithsonian American Art Museum took 1.2692079544067383s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 106.02772521972656s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.5671021938323975s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 19.173725605010986s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.4907660484313965s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.129026412963867s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5769045352935791s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 5.777725696563721s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 91.98517060279846s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.5708630084991455s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 5.785041093826294s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.822000026702881s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.6287989616394043s
Security | Sign check for Smithsonian American Art Museum took 0.5922908782958984s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.123525619506836s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.5717971324920654s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.021358728408813477s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0006740093231201172s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 1.9073486328125e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 1.3589859008789062e-05s
INFO | --- Analysis for Smithsonian took 692.3943088054657s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.19290685653686523s
Availability | VoID file availability check for Zeri Photo Archive took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.2710719108581543s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.021179914474487305s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.2636184692382812e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 1.2159347534179688e-05s
INFO | --- Analysis for Zeri-Photo-Archive took 4.231786489486694s
Availability | SPARQL endpoint availability check for Archives Hub took 20.41386079788208s
Availability | VoID file availability check for Archives Hub took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.2838919162750244s
Reputation | Calculation of the PageRank for Archives Hub took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.1920928955078125e-05s
Believability | Calculation of trust value for Archives Hub took 1.0013580322265625e-05s
INFO | --- Analysis for Archives-Hub took 53.61291813850403s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.3760275840759277s
Availability | VoID file availability check for Yale centre of British Art took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.27179503440856934s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.021224260330200195s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.2159347534179688e-05s
Believability | Calculation of trust value for Yale centre of British Art took 1.1444091796875e-05s
INFO | --- Analysis for Yale took 4.340392589569092s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 262.99204897880554s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.3176915645599365s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.022857189178466797s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 2.0742416381835938e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 1.33514404296875e-05s
INFO | --- Analysis for ADL took 537.9593176841736s
Availability | SPARQL endpoint availability check for MusicKG took 0.6581580638885498s
Availability | VoID file availability check for MusicKG took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for MusicKG took 0.27013134956359863s
Reputation | Calculation of the PageRank for MusicKG took 0.021013498306274414s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.1205673217773438e-05s
Believability | Calculation of trust value for MusicKG took 1.239776611328125e-05s
INFO | --- Analysis for MusicKG took 4.016432523727417s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.6794450283050537s
Availability | VoID file availability check for CIDOC-CRM took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.26171040534973145s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.02096104621887207s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.239776611328125e-05s
Believability | Calculation of trust value for CIDOC-CRM took 1.1920928955078125e-05s
INFO | --- Analysis for CIDOC-CRM took 3.799121141433716s
Availability | SPARQL endpoint availability check for Mondis took 0.3188929557800293s
Availability | VoID file availability check for Mondis took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Mondis took 0.26653146743774414s
Reputation | Calculation of the PageRank for Mondis took 0.021230459213256836s
Interlinking | Calculation of Degree of Connection for Mondis took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.1682510375976562e-05s
Believability | Calculation of trust value for Mondis took 1.2159347534179688e-05s
INFO | --- Analysis for Mondis took 3.320868492126465s
Availability | SPARQL endpoint availability check for DigitalNZ took 2.9188477993011475s
Availability | VoID file availability check for DigitalNZ took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.2664663791656494s
Reputation | Calculation of the PageRank for DigitalNZ took 0.023583650588989258s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.8596649169921875e-05s
Believability | Calculation of trust value for DigitalNZ took 1.049041748046875e-05s
INFO | --- Analysis for DigitalNZ took 6.712878227233887s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.15241670608520508s
Availability | VoID file availability check for Fondazione Zeri took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.26923489570617676s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.2874603271484375e-05s
Believability | Calculation of trust value for Fondazione Zeri took 1.1444091796875e-05s
INFO | --- Analysis for Fondazione-Zeri took 3.654003620147705s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.10958051681518555s
Availability | VoID file availability check for Digital Public Library of America took 0.00036454200744628906s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.2674117088317871s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.021432161331176758s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0009491443634033203s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.33514404296875e-05s
Believability | Calculation of trust value for Digital Public Library of America took 1.3828277587890625e-05s
INFO | --- Analysis for Library-of-America took 3.674866199493408s
Availability | SPARQL endpoint availability check for Auckland Museum took 1.9800646305084229s
Availability | VoID file availability check for Auckland Museum took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.27385854721069336s
Reputation | Calculation of the PageRank for Auckland Museum took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.2159347534179688e-05s
Believability | Calculation of trust value for Auckland Museum took 1.1920928955078125e-05s
INFO | --- Analysis for Auckland-Museum took 6.834810733795166s
Availability | SPARQL endpoint availability check for National Library of Spain took 1.9609980583190918s
Availability | VoID file availability check for National Library of Spain took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.2650949954986572s
Reputation | Calculation of the PageRank for National Library of Spain took 0.02063298225402832s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.0967254638671875e-05s
Believability | Calculation of trust value for National Library of Spain took 1.2159347534179688e-05s
INFO | --- Analysis for BNE took 4.903957843780518s
Availability | SPARQL endpoint availability check for National Library of Korea took 1.2481224536895752s
Availability | VoID file availability check for National Library of Korea took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.26700901985168457s
Reputation | Calculation of the PageRank for National Library of Korea took 0.021039962768554688s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.2159347534179688e-05s
Believability | Calculation of trust value for National Library of Korea took 1.1682510375976562e-05s
INFO | --- Analysis for Korea-Library took 4.203585386276245s
Availability | SPARQL endpoint availability check for The State Russian Museum took 1.2261271476745605s
Availability | VoID file availability check for The State Russian Museum took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.2724430561065674s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.0207672119140625s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.1444091796875e-05s
Believability | Calculation of trust value for The State Russian Museum took 1.1444091796875e-05s
INFO | --- Analysis for Russian-Museum took 4.181229829788208s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.60127854347229s
Availability | VoID file availability check for National Library of Scotland took 0.0003261566162109375s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.27423954010009766s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.02073359489440918s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.33514404296875e-05s
Believability | Calculation of trust value for National Library of Scotland took 1.1205673217773438e-05s
INFO | --- Analysis for National-Library-of-Scotland took 6.759416580200195s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 1.2847182750701904s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.2756314277648926s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.021715641021728516s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.1920928955078125e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 1.239776611328125e-05s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 4.448055982589722s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.18677902221679688s
Availability | VoID file availability check for OntoComedySources took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.27790260314941406s
Reputation | Calculation of the PageRank for OntoComedySources took 0.02071070671081543s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.2159347534179688e-05s
Believability | Calculation of trust value for OntoComedySources took 1.1444091796875e-05s
INFO | --- Analysis for OntoComedySources took 3.9737353324890137s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.19150304794311523s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.2646751403808594s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.022754907608032227s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.52587890625e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.2874603271484375e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 1.0967254638671875e-05s
INFO | --- Analysis for OntoCeramic-2.0 took 4.24290132522583s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.9637565612792969s
Availability | VoID file availability check for SaintGall Ontology took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.28858089447021484s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.021464824676513672s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.2159347534179688e-05s
Believability | Calculation of trust value for SaintGall Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for SaintGall-Ontology took 3.9245471954345703s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.7502279281616211s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.26433873176574707s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.02117180824279785s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.4066696166992188e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 3.8433780670166016s
Availability | SPARQL endpoint availability check for ICON took 0.26204347610473633s
Availability | VoID file availability check for ICON took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for ICON took 0.26943278312683105s
Reputation | Calculation of the PageRank for ICON took 0.020925521850585938s
Interlinking | Calculation of Degree of Connection for ICON took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ICON took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for ICON took 1.1444091796875e-05s
Believability | Calculation of trust value for ICON took 1.049041748046875e-05s
INFO | --- Analysis for ICON took 4.00719141960144s
Availability | SPARQL endpoint availability check for Polifonia took 0.24664878845214844s
Availability | VoID file availability check for Polifonia took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for Polifonia took 0.2690298557281494s
Reputation | Calculation of the PageRank for Polifonia took 0.02163529396057129s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0006847381591796875s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.4066696166992188e-05s
Believability | Calculation of trust value for Polifonia took 1.1920928955078125e-05s
INFO | --- Analysis for Polifonia took 5.58084511756897s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 1.0300395488739014s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.2771108150482178s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.02082538604736328s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.1920928955078125e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 1.1205673217773438e-05s
INFO | --- Analysis for Atlas-of-Paths took 5.085971832275391s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.1770641803741455s
Availability | VoID file availability check for Music Note Ontology took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.26999449729919434s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.021324872970581055s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.2874603271484375e-05s
Believability | Calculation of trust value for Music Note Ontology took 1.049041748046875e-05s
INFO | --- Analysis for Music-Note-Ontology took 7.9677734375s
Availability | SPARQL endpoint availability check for HaMSE took 0.19181609153747559s
Availability | VoID file availability check for HaMSE took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for HaMSE took 0.2637810707092285s
Reputation | Calculation of the PageRank for HaMSE took 0.02175736427307129s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.2874603271484375e-05s
Believability | Calculation of trust value for HaMSE took 1.33514404296875e-05s
INFO | --- Analysis for HaMSE took 4.946645498275757s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.10103464126586914s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.2717456817626953s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.021096467971801758s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.2874603271484375e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 1.0013580322265625e-05s
INFO | --- Analysis for FOod took 4.681162118911743s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.7665915489196777s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.26671457290649414s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.02167224884033203s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.3589859008789062e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 1.1444091796875e-05s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 5.023744583129883s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.3738808631896973s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.2644815444946289s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.021035432815551758s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.2636184692382812e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 1.3828277587890625e-05s
INFO | --- Analysis for ARIADNE took 5.485440015792847s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.2574653625488281s
Availability | VoID file availability check for Odeuropa Ontology took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.26753664016723633s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.021121501922607422s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.2159347534179688e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for Odeuropa took 3.2158265113830566s

--- Total time for analysis:517287.4410524368s ---
--- Total time for analysis:143.69095584789912 hours ---